Consistency interval marker assisted in-band commands in distributed systems

ABSTRACT

In-band commands may be associated with a particular consistency interval and may indicate requested actions to be performed for that consistency interval. An application may desire to perform actions, such as additional backup, snapshots, etc. on stored data, when that data is in a consistent state from the application&#39;s point of view. In order to ensure that the data is in a consistent state, a consistency interval may be created on demand. A node may request a consistency interval by sending a consistency request message to a consistency interval coordinator, which in turn, establishes the consistency interval with all nodes in the distributed environment. After sending all write requests for the consistency interval, the node may then send the command message. Command messages may be stored in consistency logs along with write requests and a replication target, or other device, may read both the write requests and the command message.

PRIORITY INFORMATION

This application claims benefit of priority to U.S. Provisional Patent Application No. 60/818,179 filed Jun. 30, 2006 titled “Consistency Interval Marker assisted In-Band Commands in Distributed Systems” by inventors Deepak Tawri and Ronald S. Karr, which is incorporated by reference herein in its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates to replication in general and, more particularly, to a method and apparatus for in-band commands using consistency interval replication.

2. Description of the Related Art

Modern distributed shared storage environments may include multiple storage objects connected via one or more interconnection networks. The interconnection networks provide the infrastructure to connect the various elements of a distributed shared storage environment. Within the storage environment, file system abstractions may be built on top of multiple storage objects. These storage objects may be physical disks or storage aggregations, like logical volumes that distribute data across multiple storage devices. As the number of logical volumes and file system abstractions grows, the complexity of the entire storage environment grows dramatically.

Storage systems frequently use data redundancy mechanisms to ensure data integrity, consistency, and availability. Other uses for data redundancy may include backing up data, distributed load sharing, disaster recovery, or point-in-time analysis and reporting. One approach to data redundancy is to copy or replicate data from a primary storage system to a second or replicated storage system. In other words, a storage system may duplicate data written to the primary copy of a data block to redundant or replicated copies of that data block in other, secondary storage systems. In some designs this copying is done synchronously when the data I/O is preformed. In other designs this replication may be performed asynchronously with the second storage system's data state lagging the primary storage state by a time interval that can be anywhere from fractions of a second to many hours, depending on the design objectives and technologies used.

Under some failure conditions, volumes that contain redundant data may require consistency recovery. For example, a host may crash during a write to a volume, or a component in the interconnect infrastructure may fail. This may leave the volume in an inconsistent state. For example, if the volume is mirrored to protect against data loss due to a single disk failure, and stores two or more complete copies of the data, a system crash during a write may leave data copies in different states and with different contents. In such situations, a consistency recovery operation may need to be performed to resynchronize the data contents and state of mirrored storage devices. One well-known synchronization method involves copying the entire contents of one data copy to another, such that all copies of data in a redundant volume have the same data contents. This process can take a very long time in even modestly sized storage configurations. To reduce the impact of consistency recovery, another well-known consistency recovery method involves maintaining a bitmap of in-progress I/Os, sometimes called “scoreboarding” or “dirty region mapping.” Every bit in this bitmap represents a region of one or more blocks of the volume. A bit in this map is set, or “dirtied”, when an I/O to the volume is issued and cleared after the I/O has completed.

SUMMARY

One goal of replication is to achieve a consistent copy of data being generated by independent streams of writes from nodes in a clustered/distributed environment. One problem that may occur is that two writes to the same block from different nodes may arrive at a replication storage target in a different order from the order in which they were written to primary storage. In consistency interval replication, as described herein, nodes send writes to the replication target freely, but the nodes may be configured to suspend writes from time to time in such a way as to achieve a point at which the data on the replication target is consistent. The replication target can then generate a snapshot or checkpoint of the data and then continue to receive writes again until the next consistency point. Consistency interval replication may involve an interval coordinator to manage the consistency points. The time between two consistency points may be considered a consistency interval. In order to obtain points in time where the replicated data is consistent, consistency interval markers may be used. Consistency interval markers may ensure that when all data writes from source nodes are completed before a consistency interval snapshot or checkpoint is generated, and thus may ensure that the data in the checkpoint is consistent. Consistency interval marker based replication may involve an interval coordinator managing the starting and stopping of individual consistency intervals and thus the timing of consistency checkpoints or snapshots.

The transition between two consistency intervals may include a two-phase process. For example, when the interval coordinator determines that an interval transition should occur (i.e. the time limit for an interval has been reached), the coordinator may first send a message informing the nodes that the current interval is ending and requesting a list of data blocks modified during that interval. In the second phase of the interval transition, the interval coordinator may analyze the list of modified blocks from each node to determine a list of conflict blocks. Conflict blocks may be data blocks written to by two different nodes during the same consistency interval. This list of conflict blocks may be delivered to each node so that the nodes may suspend writes to the conflict blocks. Once the conflicts have been resolved, the replication target may generate a snapshot or checkpoint of the data written during the ending interval and nodes may resume writes to the conflict blocks for the new interval.

When resolving write conflicts for blocks, the interval coordinator may first determine if the write conflicts for a particular block are completed or whether a completed write conflicts with a suspended in-progress write. If the conflict involves an in-progress write, the interval coordinator may request that the node sending the in-progress write, complete that write and send it to the replication target with a special indication or tag informing the replication target that the data from the in-progress write should overwrite any earlier writes (during the same consistency interval) to the same block. Thus, the later data from the in-progress write may take precedence over earlier writes to the same block—thus obviating the need to resolve any conflict between two earlier, completed writes for the same block.

If two (or more) completed writes conflict on the same block and there is no in-progress write for the block, the interval coordinator may request the latest version of the data for the conflict block from the shared storage. For instance, in one embodiment, the interval coordinator may request one of the nodes in the distributed environment to read the data for the conflict block from primary storage and forward it to the replication target with a tag similar to that used with the in-progress write, described above. Thus, a write conflict may be resolved by a node re-sending the latest version of the data for the conflict block—ensuring that the correct (i.e. latest) version of the data is included in a checkpoint or snapshot generated at the end of the consistency interval.

Consistency interval based replication may provide the ability to record or checkpoint consistent points periodically in the stream of IOs in distributed systems without compromising IO performance. Persistently recorded consistency checkpoints may give the ability to replay those points on demand to implement various asynchronous copy services, such as asynchronous mirroring, replication, snapshots, finer-granular-in-time backups for continuous data protection, etc. Additionally, such asynchronous copy services may be performed in an IO efficient and scalable manner in distributed systems.

In addition, consistency interval based replication may be used with in-band commands (IBCs) to perform various actions, such as incremental backups or snapshots of the replicated data at consistency points. For example, a command message associated with a particular consistency interval may be inserted into the replication IO stream, or may be stored in a log for replicated write requests, or, in general, into an IO replay stream at consistent points (i.e. at consistency interval boundaries) in distributed systems by creating consistency checkpoints on demand. Such in-band commands in an IO replay stream may help users (such as administrators) execute pre-planned customized operations at application defined (or other logical) points with respect to the data. Such commands may be considered in-band commands because they may be issued using the same communication or I/O channel used for communicating I/O write requests. Additionally, in-band commands may also be issued along with the write requests. In-band commands may be issued at a logical point in the IO or replay stream at which the data is in a relevant logical state (once the data for the writes have been saved to storage). In other words, an in-band command may not only be associated with a particular consistency interval, but may be sent over the same I/O communication stream during that particular consistency interval, according to some embodiments.

Consistency checkpoints, created on demand, can be used to achieve IBC functionality in distributed environments. As noted above, users may issue customized in-band commands at application specific logical (consistent) points on any node in a distributed system, according to some embodiments. The given command may be inserted in the IO stream at a consistency interval boundary while storing (or spilling) the IOs to logs, such as persistency spillover logs, or in the replication stream while sending writes to replication target. Logged IBCs may also be used to trigger in-band actions or events at known application-based logical points in the data on a primary data volume, such as when the logs are replayed for snapshot, intelligent backup or other purposes. Similarly, IBCs may also trigger actions or events on secondary storage (target) when logs are replayed for replication purposes. In general, in-band commands may be used to coordinate virtually any activity performed on replicated data.

For example, writes may be issued to a volume (or other storage system or device) by an application running on multiple nodes in a distributed or clustered system. Apart from updating the volume set, the nodes may log the writes into persistent spillover log(s) or they may send the writes to the replication target system directly. For example, in-band commands issued by a first node may be injected into a log stream (or could be injected in the message stream to the replication target device) at the end of a consistency interval. In other words, in-band commands may be recorded persistently into a node's log after the node logs all of the data for a consistency interval. When that log is replayed to get incremental backup, to refresh snapshots or to replicate the data, the in-band command may be read from the log and may be executed after replaying the data of the relevant consistency interval when data on the target volume set would have reached a consistent point, according to some embodiments. Thus, in-band commands implemented using consistency interval marker based replication may, in some embodiments, provide a way for application checkpointing in IO replay/replication streams of distributed systems.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram illustrating a network environment in which consistency interval marker based replication may be implemented, in one embodiment.

FIG. 2 is a block diagram that illustrates the logical association between nodes, the replication target and replicated data, according to one embodiment.

FIG. 3 is a block diagram illustrating, according to one embodiment, the logical flow of communication between a node, an interval coordinator, and a replication target while implementing consistency interval marker based replication.

FIG. 4 is a flowchart illustrating one embodiment of a method for consistency interval based replication.

FIG. 5 is a block diagram illustrating, according to one embodiment, a first stage of block conflict resolution, as described herein.

FIG. 6 is a block diagram illustrating, according to one embodiment, a first stage of block conflict resolution, as described herein.

FIG. 7 is a block diagram illustrating the logical communication flow between a node, an interval coordinator, and a replication target while implementing consistency interval replication with block conflict resolution, according to one embodiment.

FIG. 8 a flowchart illustrating one embodiment of a method for block conflict resolution, as described herein.

FIG. 9 is a flowchart illustrating one embodiment of a method for solving block conflicts within block conflict resolution, as described herein.

FIG. 10 is a flowchart illustrating one embodiment of a method for implementing in-band commands using consistency interval marker based replication.

FIG. 11 is a flowchart illustrating one embodiment of a method for receiving and executing in-band commands using consistency interval marker based replication.

FIG. 12 is a block diagram illustrating storing write requests and in-band commands to persistent spillover logs during consistency interval marker based replication, in one embodiment.

FIG. 13 is a flowchart illustrating one embodiment of a method for implementing in-band commands using persistent spillover logs with consistency interval marker based replication.

FIG. 14 illustrates one embodiment of the logical flow of communication between nodes and an interval coordinator regarding timestamps for replicating data to a temporal volume.

FIG. 15 is a flowchart illustrating one embodiment of a method for using on-demand consistency interval marker based replication with temporal volumes.

FIG. 16 is a block diagram illustrating the logical flow of communication between nodes and an interval coordinator regarding timestamps for replicating data to a temporal volume, according to one embodiment.

FIG. 17 is a flowchart illustrating one embodiment of a method for using periodic consistency interval replication with temporal volumes.

FIG. 18 is a block diagram illustrating offline feeding of temporal volumes using persistent spillover logs and consistency interval marker based replication, in one embodiment.

FIG. 19 is a flowchart illustrating one embodiment of a method for offline feeding of temporal volumes using persistent spillover logs and consistency interval marker based replication.

FIG. 20 is a block diagram illustrating a computer system capable of implementing consistency interval marker based replication and/or block conflict resolution in a networked environment, according to one embodiment.

While the invention is described herein by way of example for several embodiments and illustrative drawings, those skilled in the art will recognize that the invention is not limited to the embodiments or drawings described. It should be understood, that the drawings and detailed description thereto are not intended to limit the invention to the particular form disclosed, but on the contrary, the intention is to cover all modifications, equivalents and alternatives falling within the spirit and scope of the present invention as defined by the appended claims. The headings used herein are for organizational purposes only and are not meant to limit the scope of the description or the claims. As used throughout this application, the word “may” is used in a permissive sense (i.e., meaning having the potential to), rather than the mandatory sense (i.e., meaning must). Similarly, the words “include”, “including”, and “includes” mean including, but not limited to.

DETAILED DESCRIPTION OF EMBODIMENTS Consistency Interval Marker Based Replication

Consistency interval marker based replication, as described herein, may be implemented on distributed or clustered computing environments, such as the one illustrated in FIG. 1. As shown in FIG. 1, a set of source nodes, such as nodes 110, 112 and 114 may write data to one or more primary storage devices, such as primary storage 130 and may also replicate the data writes to a replication target, such as replication target 140. The system illustrated in FIG. 1 may implement consistency interval marker based replication, as described herein. Consistency interval marker based replication may, in some embodiments, involve a two-phase distributed algorithm to obtain consistent snapshots, which also may be referred to as consistency points, or global snapshots, of data across the nodes in the distributed environment. Such consistent snapshots of data may facilitate various data copy and replication image services in the distributed environment. For example, consistency interval replication may provide periodic consistency checkpoints for crash recovery. A consistency interval may be defined as the time between two consecutive consistency points. In general, a consistency interval may begin just after one consistency point and end just before the next. Similarly, a consistency point includes data written during the previous consistency interval.

While consistency interval marker based replication is described herein mainly in reference to write requests from applications, file systems, volume managers and similar processes to storage devices, in general, consistency interval marker based replication may be utilized to provide consistent points or snapshots for any type of data stream. For example, consistency interval replication may provide consistency checkpoints or snapshots across collections of logs, across collections of storage objects, or across sets of message streams in the distributed or clustered environment. Please note that the terms “I/O” and “write” are both used interchangeably herein to refer to data written by a source node to the replication target during consistency interval marker based replication. Please further note that the term “application” is used to refer to any processes executing on source nodes and replicating data to a replication target. Thus, “application”, as used herein may refer to a volume manager, file system, database application, storage replicator, or an end-user application, as well as any other processes replicating data.

When implementing consistency interval marker based replication, data written to primary storage 130 may also be replicated to replication target 140. Each actual data write from a node, such as from node 110, may include an identifier of the current consistency interval. An interval coordinator, such as interval coordinator 120 may determine and distribute IDs for each consistency interval and may also determine the length of each interval and manage the transitions between intervals. Consistency intervals may be of various lengths and the length of each interval may be determined in any of numerous methods, according to various embodiments. For example, in one embodiment, all consistency intervals may be same length of time, say 5 seconds. In other embodiments however, consistency interval length may be based upon the amount of data replicated or the number of write requests during that consistency interval. In yet other embodiments, consistency intervals may be determined by an application which is generating data changes (e.g. a database application) and sets interval markers according to this application's view of data consistency (e.g. on transaction commits, or other consistency events recognized by such applications as appropriate recovery and restart points). Thus, in some embodiments, the transition between consistency intervals may be created on demand by applications. For instance, in some embodiments, an application, such as application 150 may request consistency interval transitions to support in-band commands. In other embodiments, on-demand consistency interval transitions may be requested to support temporal versioning of temporal data. Replication may be generally asynchronous in that the storage subsystem may complete the I/O to the application before it is replicated. This differs from the writes to base or primary storage, which generally don't complete to the application that submitted the I/O until it is completed on the base storage.

As noted above, interval coordinator 120 may manage the transitions between consistency intervals. For example, interval coordinator 120 may determine when the current interval should end and the next begin. Interval coordinator 120 may ensure that the data replicated during an interval is consistent, i.e. that that no write replicated during that interval depends upon a write that has not yet been replicated by the end of that interval. At the start of each consistency interval the interval coordinator may send a message to all source nodes in the distributed environment informing them of the new interval and possibly including an interval identifier to be included in writes from each node to the replication target. When sending a message, the consistency interval coordinator may utilize any suitable method of communication. In general, the term “message”, as used herein refers to the communication of information via any suitable method and/or transport. At the end of each interval the interval coordinator may also send a message to all nodes informing them that the interval is over. In some embodiments, a single interval transition message may be used to signal the transition between two consistency intervals. The individual nodes may, in some embodiments, be configured to suspend the completion of writes during the transition period between intervals. Suspending write completions may allow all in-progress writes from source nodes to complete and thus may allow the data to be consistent when the replication target checkpoints or saves a snapshot for the consistency interval. Thus, when transitioning between intervals, the interval coordinator may signal each node that the current interval has ended and, in response, each node may begin including the new interval's ID with each write to replication target 140.

After sending an interval end message to each node, the interval coordinator may wait for an acknowledgment from each node before proceeding. This may allow for discovery of a crashed node. For example, if a node fails to respond or acknowledge a message from the interval coordinator, the interval coordinator may determine that the node has failed (or crashed) and may initiate recovery procedures for that node, as described below. After interval coordinator 120 has received an acknowledgment from every node, it may then send an interval start message informing nodes to complete held writes and to begin using the new interval's identifier in writes to replication target 140.

When switching between intervals, each node may also be configured to send a consistency interval marker message to the replication target. For example, each node may send a message indicating that it has finished sending all writes for the current consistency interval. In other embodiments, each node may add a consistency interval marker or other indication of the interval transition into the first write message of a new interval. In yet other embodiments, each node may be configured to include sequence numbers with every write during an interval and such sequence numbers may roll over or reset at interval transitions. Thus, in some embodiments, the combination of a new interval ID and a sequence number rollover may indicate to the replication target a consistency interval marker for a particular node. When including sequence numbers with writes, each node may maintain its own sequencing and thus the sequence number may be considered node-specific. In yet other embodiments, the nodes may only be configured to include the new interval's ID with writes to the replication target and the replication target may consider the first write from a node that includes the new interval's identifier to be a consistency interval marker in the I/O stream.

Alternatively, in other embodiments, each node may send a consistency interval marker message to the interval coordinator rather than to the replication target. The interval coordinator may then send a single consistency interval marker message to the replication target after receiving individual consistency interval marker messages from the source nodes. Thus, in some embodiments, the replication target does not have to keep track of which nodes have sent consistency interval markers, but instead may rely upon the interval coordinator to send a single consistency interval marker message informing the replication target that all activity for the current interval is complete and that a checkpoint or snapshot for this interval may be saved/written.

In some embodiments, the replication target may save or store the writes received from nodes during a consistency interval in a log or other data structure separate from the main storage volume(s) for the replicated data. In some embodiments, writes from nodes may be stored in a persistent log for recovery purposes. Once the consistency interval is over and the nodes have indicated that all their data has been sent, the replication target may read the saved writes to create a snapshot or checkpoint of the data on replication storage volumes, sometimes called secondary storage. When checkpointing data for a consistency interval, the replication target may store only the changes to data made during the consistency interval, rather than make a complete copy or snapshot all the data. Thus, in some embodiments, a single consistency checkpoint may only include changes to the data made since a previous consistency checkpoint.

In other embodiments, however, a replication target may not log or spool the writes as they are received, but instead may store the data from writes to the replicated storage volumes immediately upon receipt from a node. Writing data immediately to replicated storage volumes may save time when processing the end of a consistency interval. However, it may be necessary to save complete snapshots of the data at each consistency point, rather than merely storing the data changes between two consistency points.

After receiving consistency point messages from every source node in the distributed or clustered environment, replication target 140 may notify interval coordinator 120 of that fact, according to some embodiments. In response, interval coordinator 120 may send an interval start message to the source nodes indicating the start of the new interval.

In some embodiments, each node may register with the interval coordinator or the replication target before sending writes. For example, node 110 may register with interval coordinator 120 and in response interval coordinator 120 may send node 110 the current interval identifier. In some embodiments, new nodes may join the replication process at any time, while, in other embodiments, new nodes may only be able to join at the start of a new consistency interval.

Block Conflict Resolution

Consistency interval marker based replication, as described herein, may be implemented for systems in which the data written by nodes 110, 112 and 114 is read-shared, but not write-shared, according to some embodiments. That is, no two nodes may be able to write to the same storage block of data at the same time. When implementing consistency interval marker based replication in a write-shared environment, however, block conflict resolution may be utilized to ensure consistent data at consistency interval transitions. For example, when two nodes write to the same block of data during the same consistency interval, the system may use block conflict resolution to ensure the consistency of the data for that block within the consistency interval. When implementing block conflict resolution, interval coordinator 120 may track data blocks being written to by the nodes. Interval coordinator 120 may identify a block conflict when two nodes write to the same data block during the same consistency interval. When resolving such block conflicts, the interval coordinator may send a list of blocks with conflicts to each node. For example, if node 110 and node 112 each write to a particular data block, the interval coordinator may send an indication or identifier of the data block, such as the logical or physical storage address of the data block, to all nodes during the interval transition. Alternatively, in other embodiments, interval coordinator 120 may send an indication or identifier of the write requests, such as node specific sequence numbers, to the nodes that caused a block conflict. In response, the source nodes may be configured to suspend all writes to the conflict blocks until the conflicts can be resolved. Additionally, the interval coordinator may be configured to resolve conflicts by determining or “proving” the ordering of the writes to the conflict blocks.

For example, in one embodiment, the particular writes from one node may be determined to be earlier than conflicting writes from another node, thus “proving” that the writes do not actual conflict so long as the ordering between those writes is maintained and communicated properly to the replication target.

In order to determine a list of conflict blocks, interval coordinator 120 may query every node to obtain a list of blocks written to by that node. Alternatively, each node may periodically send such a list of modified blocks to the interval coordinator during each interval. For example, each node may send a list of modified blocks at regular intervals, such as according to some fraction of the overall interval time length. For instance, in one embodiment, a node may be configured to send a list of modified blocks 5 times during an interval. In other embodiments, a node may be configured to send a list of modified blocks during idle time between write requests. Alternatively, in yet other embodiments, a node may be configured to send a list of modified blocks after a certain number of writes or after a predetermined number of blocks have been modified. Interval coordinator 120 may be configured to compare the blocks modified by each node to determine a list of conflict nodes that were written to be more than one node during the current interval, according to some embodiments. When informing the nodes of any block conflicts, interval coordinator 120 may include a list of conflict blocks in the interval end message, or in a specific block conflict message. Additionally, in some embodiments, interval coordinator 120 may be configured to initially send a preliminary list of block conflicts and subsequently send a final or updated list of block conflicts.

As noted above, source nodes, such as nodes 110, 112, and 114, may send lists of modified blocks to the interval coordinator from time to time during a consistency interval. Rather than sending a message after every write, nodes may collect a list of modified blocks and send a single message including a list or batch of modified blocks. Nodes may include ranges of modified blocks rather than individually list contiguous blocks. As described above, the period used for sending list of modified block may be some fraction of the interval period itself Alternatively, each node may send its list of modified blocks whenever that list exceeds some predetermined number of modified blocks. In general, each node may only include a modified block on a single list to the interval coordinator. Thus, even if a block is modified multiple times during the same consistency interval, it may only be included in only one list message to the interval coordinator, according to certain embodiments. Each time interval coordinator 120 receives a list of modified blocks from a node, interval coordinator 120 may merge the latest list with earlier lists. In general, interval coordinator 120 may be configured to maintain a single list of modified blocks for each node and to merge newly received lists of modified blocks into this single list, according to one embodiment. Additionally, interval coordinator 120 may maintain multiple such lists, one for each node. A node may also send a list identifying each individual modified block or, alternatively, may send ranges of modified blocks to save time, effort, and bandwidth. In general, any suitable method for identifying multiple data blocks may be used to send a modified block list from a node to the interval coordinator, according to various embodiments.

In general, interval coordinator 120 may send the list of block conflicts to all nodes in the distributed or clustered environment. In some embodiments, the interval coordinator may send such a list of block conflicts after sending an interval end message, but prior to sending the interval start message. In response to receiving a list of conflict blocks, each node may be configured to suspend any new writes for data blocks on the conflict list until the conflicts have been resolved and a new interval has begun. Additionally, in response to receiving a list of conflict blocks, each node may respond with an updated list of blocks modified after receiving the initial interval end message. For example, some writes may be in process when a node receives an interval end message from interval coordinator 120 and thus the blocks modified by those writes may not have been included in any list of modified blocks previously sent to the interval coordinator. In some embodiments, interval coordinator 120 may then use the updated or final lists of modified blocks from each node to determine a final list of conflict blocks and may distribute the final list of conflict blocks to the every node.

Interval coordinator 120 may resolve conflicts to data blocks in various ways. In general, interval coordinator 120 may consider two different types of write conflicts. Firstly, two or more writes may modify the same block during the same consistency interval. The replication target may receive two writes to the same data block by two different nodes in a different order than the order in which those writes were originally completed on the primary data storage. In other words, there may exist an ordering ambiguity between the two writes. For example, node 110 may write a particular data block and node 112 may subsequently overwrite node 110's write with another write to that same data block. However, it may be possible, due to network congestion or other issues, that when the writes to that data block are sent to replication target 140 they arrive out of order. Thus, while node 112 may have actually written to the data block last, its write may arrive first to replication target 140. Without recognizing and resolving such block conflicts a checkpoint or snapshot for the current interval may include the wrong version of data for blocks written to be more than one node, in some embodiments. Thus, any recovery made using such a snapshot may result in data corruption.

In general, replication target 140 and interval coordinator 120 may have no way of knowing the proper order of multiple writes to a single data block, and thus no way of resolving the ordering ambiguity. In order to ensure that the consistency checkpoint or snapshot generated at the end of the current consistency interval has a correct (i.e. consistent) version of the data, the data block may be read from primary storage 130 and sent to replication target 140, in certain embodiment. In some embodiments, interval coordinator 120 may request that a particular node read the data for a conflict block from primary storage 130 and forward it to replication target 140. In other embodiments, however, interval coordinator 120 may be configured to directly read the data from primary storage 130 and forward it to replication target 140.

In some embodiments, writes conflicts may be resolved by determining the correct ordering of conflicting writes to a data block using specific knowledge of the data being written. For example, in one embodiment, the replicated data may be for a shared database and replication target 140 may be able to inspect the contents of each conflicting write and determine from the individual contents of each write their correct ordering. For instance, in one embodiment, each write to the database may include a timestamp or a global sequence number that may allow replication target 140 to determine the correct ordering of writes. In other embodiments, however, replication target 140 and interval coordinator 120 may not be able to determine the correct ordering of conflicting writes to the same data block and thus may read, or cause to be read, data for the conflict block from primary storage 130 to ensure that the replicated data is consistent with the primary data at the time of the consistency interval transition, and thus, when a consistency checkpoint or snapshot is generated.

One benefit to having source nodes, such as nodes 110, 112, and 114, suspend writes and/or write completions during consistency interval transitions is that it allows data for a conflict block to be read from primary storage 130 before any of the nodes overwrite that block during the next interval, according to some embodiments. Thus, if source nodes are allowed to continuing writing data during consistency interval transitions, one of the nodes may overwrite a conflict block, thus preventing interval coordinator 120 and/or replication target 140 from resolving that conflict by obtaining the latest version of data for that block from primary storage 130.

Alternatively, as noted above, there may also be conflict between one or more completed writes to a data block and an in-progress or uncompleted write to the same data block. For example, when the current interval ended, a node may have suspended a write to a conflict block. In such a case, interval coordinator 120 may request, via a message or any other form of communication, that the node holding the suspended in-progress write completion that write including a special indication that the write completion is resolving a conflict and that the write should overwrite early writes to the conflict block and therefore be included in any checkpoint or snapshot generated for the just ended interval. By requesting completion of the in-progress write, interval coordinator 120 may eliminate the need to determine the order of other, previously completed, writes to the same block, and may also avoid a read operation to get the last written version of the data.

If interval coordinator 120 and/or replication target 140 cannot resolve a conflict block, such as in the event that one of the nodes has crashed or running very slowly or if the block cannot be read from primary storage 130, the current interval may be considered invalid and combined with the next interval to make one, larger interval, as will be discussed in more detail below.

After resolving all block conflicts, interval coordinator 120 may send a message to all nodes informing them that the current interval is closed and that all writes and write completions may be resumed, in some embodiments. The interval coordinator may also send a completion message to the replication target regarding the successful resolution of all block conflicts. In response, the replication target may generate a consistency checkpoint or snapshot of the data, thereby creating a consistency point in the replicated data corresponding to the end of the consistency interval. Alternatively, in other embodiments, each source node may be configured to send consistency interval markers to the replication target after completing all processing, including conflict resolution processing, for the current interval. Thus, the replication target may generate a consistency point or snapshot in response to receiving consistency interval markers from every node, according to some embodiments.

In some embodiments, interval coordinator 120 may send a single message that serves multiple purposes to nodes. For example, in one embodiment, the interval coordinator may send a custom message to each node that includes: a final list of block conflicts, permission to resume writes for non-conflict blocks, a list of blocks the node should forward from primary storage to the replication target, and a list of in-progress writes that the node should complete to resolve block conflicts. In response to such a message, each node may be configured to resume writes to non-conflict blocks, send the requested nodes to the replication target, complete the designated in-progress writes, and send a consistency interval marker message to the replication target (and/or the interval coordinator), according to some embodiments. As noted above, when the replication target (and/or interval coordinator) receives a consistency interval marker message from every node, processing for the current interval may be considered complete and a checkpoint or snapshot of the data may be generated. Thus, in some embodiments, the interval coordinator may send individual messages for each step of the block resolution process, while, in other embodiments, the interval coordinator may send a single message to each node containing all the information that node needs in order to complete interval transition processing and block conflict resolution.

In some embodiments, the nodes may be configured to start sending data for a new consistency interval before all block conflicts for the current interval have been resolved. Thus, the replication target may receive writes for a new interval while also receiving conflict resolving writes for the current interval. Accordingly, replication target 140 may, in some embodiments, be configured to maintain separate write logs, not only for each node but also for each active interval. Once all block conflicts for the current ending interval have been resolved and the consistency checkpoint generated, replication target 140 may be configured to delete or otherwise clean up the write logs for the current interval, in one embodiment.

While the above description of block conflict resolution generally refers to either the interval coordinator or the replication target resolving write conflicts on blocks, in some embodiments, a separate shared-write coordinator or block coordinator may resolve such conflicts. For example, in some embodiments, a shared-write coordinator, such as shared-write coordinator 150 may be configured to resolve write conflicts. Interval coordinator 120 may forward a list of conflict blocks to shared-write coordinator 150 during the interval transition and rely upon shared-write coordinator 150 to resolve the conflicts. Shared-write coordinator 150 may perform the same functions to resolve write conflicts described above regarding interval coordinator 120. Additionally, both interval coordinator 120 and shared-write coordinator 150 may reside on a single device or may be part of replication target 140, according to various embodiments. Also, in some embodiments, the number and length of intervals used by the interval coordinator and the shared-write coordinator may not be the same. For instance, there may be more shared-write intervals as long as consistency intervals correspond to a shared write coordination interval.

Thus, in some embodiments, replication target 140 may perform all the functionality of a replication target, an interval coordinator and a shared-write coordinator. In another embodiment, however, interval coordinator 120 may perform all functionality of both an interval coordinator and a shared-write coordinator separately from replication target 140. Furthermore, interval coordinator 120 and/or shared-write coordinator 150 may reside on virtually any node in the distributed or clustered environment, such as on any of nodes 110, 112 and/or node 114, as well as on replication target 140, or may also reside on a separate, dedicated device or devices.

When implementing consistency interval marker based replication in a write shared situation, interval coordinator 120 may, during a consistency interval transition and before resolving block conflicts, request that all nodes suspend writes to the blocks in conflict. Thus, in some embodiments, each node may temporarily suspend all writes to all blocks and then, after receiving a list of conflict blocks (whether provisional or final), resume writes to block that are not on the block conflict list. However, source nodes may be configured to include such writes to non-conflict blocks as part of the next, new consistency interval, rather than the currently ending interval. Additionally, in some embodiments, when writes cross the consistency interval boundary, some writes may be assigned to one interval and others may be assigned to a next interval. As noted above, nodes may include the interval ID along with writes, allowing the replication target to distinguish between writes for different consistency intervals during a consistency interval transition. In some embodiments, Nodes may suspend writes to conflict blocks until receiving a message from interval coordinator 120 confirming that all conflicts have been resolved.

When implementing consistency interval marker based replication, as described herein, replication target 140 may store received writes in one or more logs, according to some embodiments. In one embodiment, replication target 140 may maintain a separate write log for each node, while in other embodiments, replication target 140 may maintain only a single log file, but may include a node identifier when storing the writes. Thus, in general, replication target 140 may be configured to store (and access) each received write on a node-specific basis. Alternatively, in one embodiment, only interval identities and node-specific interval completions may be logged.

Additionally, recovery information, such as in-progress writes “scoreboards”, synchronous write logs, or other types of recover information, may be maintained for the data being replicated. Thus, in the event of a node (either a source node, the interval coordinator or a shared write consistency coordinator) crashing, the recovery information may be used to reconstruct a consistent data image for replication. For example, when maintaining an in-progress writes scoreboard using a bitmap, individual bits representing ranges or regions of data storage are marked (e.g. set to 1) when the corresponding region is modified/written to. A bit may be cleared when writes to the corresponding region have been completed and/or logged successfully. In the event of a node crashing, the recovery information may be used to determine those regions of the data that must be rebuilt or made consistent for the replicated backup. While in some embodiments, replication target 140 may maintain both node-specific write logs and recovery information, in other embodiments, either the write logs, the recovery information or both may be maintained by the source nodes or by one or more other processes/entities in the distributed environment. In general, any method or manner of persisting a particular write may be used as long as information that the particular blocks were modified can be retained (or at least recovered) between the times blocks are written to the primary storage until all replication processing is complete.

Target Controlled Consistency Interval Replication

In some embodiments, a replication target, such as replication target 140, may perform some or all of the same functions as an interval coordinator. Thus, the replication target may send out interval start and end messages as well as track and resolve block conflicts. When utilizing target controlled consistency interval replication, source nodes, such as nodes 110, 112 and 114, may initially register themselves with replication target 140 and replication target 140 may respond by sending each node the current interval ID, according to some embodiments. As the nodes send writes, replication target 140 may store a copy of each write in a node-specific log and may also maintain a list of blocks modified by each node. Thus, when implementing target controlled consistency interval replication, the replication target may stream, or store, the received writes into logically separate logs and may also retain copies of the blocks written in memory, again logically separated by source (i.e. node).

Additionally, replication target 140 may maintain a list of block conflicts needing resolution. When an interval ends, replication target 140 may not have to request lists of modified blocks from the nodes as it may already have this information from the individual writes, according to some embodiments. The resolution of individual block conflicts may be performed as described above when using a separate consistency interval coordinator, in some embodiments.

At the end of a consistency interval, replication target 140 may, in some embodiments, send a message to all nodes signaling the end of the current interval. In one embodiment, each node may send a specific acknowledgment message to replication target 140 in response to the interval end message, while, in other embodiments, nodes may not send a specific acknowledgement message but instead may merely begin including the new interval's ID in writes to the replication target as an acknowledgement of the interval transition. However, if a node has no new write operations to send to the replication target, a specific interval end message may be required in some embodiments.

After a consistency interval has ended, replication target 140 may not immediately generate a consistency checkpoint or snapshot, according to some embodiments. Instead, in some embodiments, the replication target may hold the accumulated writes for one or more additional intervals to ensure that any writes arriving late (i.e. after the end of the interval) may also be included in the generated checkpoint or snapshot. Thus, in some embodiments, replication target 140 may include node-specific write logs for more than one interval. For example, replication target 140 may, in one embodiment, be configured to wait two consistency interval lengths before generating a checkpoint for a consistency interval. Thus, while receiving writes during consistency interval 3, replication target 140 may, in some embodiments, be holding the received writes for intervals 1 and 2. Once interval three has ended, the replication target may then generate a checkpoint or snapshot of the data from interval 1, according to one embodiment. In some embodiments, replication target 140 may not perform any conflict resolution processing until after waiting sufficient time to ensure the receipt of any late arriving writes. In other embodiments, however, replication target 140 may analyze and perform conflict resolution immediately after an interval as ended and perform additional conflict resolution if required by late arriving writes.

Another method, according to some embodiments, to help ensure that all writes for a consistency interval have been received before generating a checkpoint or snapshot, may be to have the source nodes include a node-specific sequence number with each write sent to the replication target. Thus, in some embodiments, replication target 140 may be configured to determine that one or more writes have not been received, based on the sequence numbers, and request the resending of those writes. Alternatively, in other embodiments, each node may be configured to send a list of IDs for the writes associated with a consistency interval, thus allowing the replication target to verify that it has received all the writes sent by the node. In one embodiment, each node may include node-specific sequence numbers and may also include the sequence number of the last write sent in an acknowledgement to an interval transition message from replication target 140. In general, consistency interval marker based replication, with or without block conflict resolution, may include the ability for a replication target to determine whether or not it has received all the writes sent from source nodes during a consistency interval before generating a consistency checkpoint or snapshot for that interval.

When including block conflict resolution in target controlled consistency interval replication, replication target 140 may compare the writes it has received from all source nodes to determine whether there are any block conflicts, i.e. two nodes writing to the same block during the same consistency interval. In some embodiments, the replication target may be able to determine the correct ordering of writes to a single block. For example, in one embodiment, replication target 140 may have specific knowledge of the structure and/or nature of the data being written, such as for a custom database application, and thus may be able to use the content of writes to determine their proper ordering. For instance, as described above, the replication target may be able to use sequence numbers, transaction IDs or other characteristics of the data being written to determine the correct ordering of the writes and thus, the final (i.e. correct) state of the block at the end of the consistency interval.

Additionally, in some embodiments, the source node may include node-specific timestamps in each write sent to replication target 140 and replication target 140 may be able to determine the proper ordering of multiple writes to a single block based upon those timestamps. However, since individual clocks used for timestamps from different nodes may be skewed with respect to each other, replication target 140 may only be able to determine the correct order for writes sent sufficiently apart in time to overcome skew and drift between the source nodes' individual clocks, according to one embodiment. Thus, even if nodes include timestamp information with each write, replication target 140 may not be able to always determine the proper ordering of writes sent close together in time.

If replication target 140 cannot determine the proper ordering of multiple writes to a single block, replication target 140 may be configured to request that one of the nodes, such as node 110, read the block from primary storage 130 and forward it to replication target 140, as described above regarding interval coordinator 120. As noted above, the data read from the primary storage 130 may not be valid if any node has overwritten the relevant block during a later consistency interval. Replication target 140 may, in one embodiment, be configured to search node-specific write logs for later intervals when determining whether or not a conflict block was overwritten in a later interval. Thus, in some embodiments, the nodes may be configured to suspend writes to conflict blocks until all conflicts have been resolved, as discussed above.

Combining Consistency Intervals

If a conflict block was overwritten during a later interval before the conflict was resolved, the current consistency interval may be declared invalid and combined with one or more later intervals, according to one embodiment. For example, replication target 140 may use a 1 second consistency interval length, and may have generated a consistency checkpoint for a consistency interval ending at time 2:15:59. If, in this example, the consistency interval ending at 2:15:30 includes two writes to the same block for which the proper ordering cannot be determined, replication target 140 may search the write logs for the consistency interval ending at 2:15:31 for writes to the same conflict block. If, the consistency interval ending at 2:15:31 includes only a single write to the conflict block, or alternatively, two or more writes for which the ordering can be determined, that data may be used for the conflict block and the two consistency intervals (ending at 2:15:30 and 2:15:31, respectively) may be combined into single, two second consistency interval, according to some embodiments. Thus, replication target 140, in this example, may not store a consistency checkpoint for the consistency interval ending at 2:15:30, in one embodiment.

If, using the same example from above, the consistency interval ending at 2:15:31 also included multiple writes to the conflict block and the ordering of those writes cannot be determined, replication target 140 may search yet later consistency intervals for the contents of the conflict block. If say, the consistency interval for 2:15:32 does not include any writes to the conflict block, the replication target may, in some embodiments, request that a node, such as node 110, read the contents of the block from primary storage 130, which would represent the correct contents of the block at the end of the 2:15:31 interval (since no node has overwritten it since). Replication target 140 may, in some embodiments, then use that data to resolve the conflict for the block in question and combine the two consistency intervals ending at 2:15:30 and 2:15:31 into a single, 2 second, interval, as described above. Please note, that in both of the above cases, the state of the replicated data may not be consistent at 2:15:30, but may be consistent at both 2:15:29 and 2:15:31. In another example, one node may be slower to respond to an interval completion message than two other nodes that may respond more quickly. Thus, any conflicts between the two quicker nodes may already be resolved by the time the first node does respond to the interval completion message. When the first node does respond, it may or may not have additional conflicts with the other two nodes. If the first node does not conflict with any writes from the other two nodes, no further conflict resolution is required.

In general, consistency interval marker based replication may be seen as a means for coordinating across virtually any collection of data sources which need to be copied or replicated for various copy services, or that need to be asynchronously processed for various other services. Additionally, consistency interval marker based replication may be implemented for any collection of systems that share one or more data volumes and replicates to other, secondary volumes, according to various embodiments. The data sources for consistency interval marker based replication may represent any level of the typical I/O stack. For instance, volume managers, file systems, databases storage replicators (in hardware or software), and end-user applications are a few types of data sources for which consistency interval marker based replication may be utilized. When implementing consistency interval marker based replication, various asynchronous copy services may be performed in a generally I/O efficient and scalable manner in clustered and/or distributed environments including multi-host environments. Such asynchronous copy services may include, but are not limited to asynchronous mirroring, replication, snapshots, finely grained in-time backups for continuous data protection, among others.

Please note that the networked computing environment illustrated in FIG. 1 represents only one possible environment in which consistency interval marker based replication, with or without block conflict resolution, may be implemented. For example, network 100, as illustrated in FIG. 1, may comprise any of various network technologies according to various embodiments. Network 100 may be a local area network, wide area network, intranet network, Internet network, or many other types of network. Network 100 may be designed to be continuously available (although network outages may occur), or may be intermittent (e.g. a modem connection made between a computer system in a user's home and a computer system in a user's workplace).

Network 100 may utilize any of a number of different physical networking technologies including, but not limited to, Fiber Channel, Ethernet, Fast-Ethernet, Gigabit-Ethernet, Myrinet, Infiniband, VAX CI, or ServerNet, or others. Network 100 may be configured according to a number of different network topologies including, but not limited to, star, ring, token-ring, token-bus, scatternet, dual-ring, mesh, etc. Network 100 may also be configured to utilize a combination of different networking technologies and/or topologies. Additionally, Network 100 may comprise shared storage or shared memory for communicating between different computer systems or between processes within the same computer system, according to various embodiments.

In some embodiments, Network 100 may be the interconnect network for any of various distributed shared storage environments, including, but not limited to, network file system (NFS), common Internet file system (CIFS), storage area network (SAN), network attached storage (NAS), storage-network aggregation, multi-site block storage, object-based storage devices (OBSDs), or other asymmetric, out-of-band, or shared storage models. Furthermore, the network environment illustrated in FIG. 1, may represent any of various types of distributed or clustered networking environments, according to various embodiments. For example, in one embodiment, consistency interval marker based replication may be implemented in a distributed environment, such as a multi-node system in which blocks of data on a storage volumes are virtualized across various nodes in the distributed environment, or in a clustered environment, such as a multi-node system in which all volume data is distributed uniformly across all nodes sharing the volumes.

Similarly, nodes 110, 112 and 114 may, in different embodiments, represent any of a number of different types of applications and/or processes at various levels in an I/O stack, such as volume managers, file systems, databases storage replicators (in hardware or software), and end-user applications, among others. Additionally, primary storage 130 and replication target 140 may represent any of various sorts of single node or multi-node storage devices and/or storage systems including, but not limited to, disk drives, disk arrays, storage controllers, array controllers, tape drives, optical drives, tape libraries, RAID systems, and/or object based storage devices (OBSD).

Various aspects of consistency interval marker based replication and block conflict resolution will be described in more detail below.

FIG. 2 is a block diagram illustrating the relationship between source nodes 110, 112 and 114, replication target 140, and the replicated data, according to one embodiment. As described above, multiple source nodes, such as node one 110, node two 112, and node three 114, may send write requests to replication target 140 asynchronously from the I/O stream to primary storage 130. In some embodiments, the message used to send a write to replication target 140 may include a current interval identifier. For example, node one 110 may send write message 200 to replication target 140 and may include interval identifier 210 in the message. Thus, in the embodiment and example illustrated by FIG. 2, node one may send writes during consistency interval 3. While, simple, numeric interval identifiers are used herein by way of example to identify consistency intervals, in other embodiments, more complex interval IDs, such as ones including date/time information, replication target information, or even universally unique global identifiers, may be also used.

As described previously, replication target 140 may maintain multiple node-specific write logs to store the writes from nodes during consistency interval. Thus, as illustrated in FIG. 2 according to one embodiment, replication target 140 may maintain three separate write logs, node one write log 220, node two write log 230, and node three write log 240, to store write I/Os from node one 110, node two 112, and node three 114, respectively. Additionally, in other embodiments, replication target 140 may also maintain different sets of node-specific write logs for different consistency intervals, as noted above. For example, replication target 140 may, in one embodiment, be configured to hold the writes for a previously ended consistency interval while collecting writes for a later consistency interval. Thus, while FIG. 2 illustrates node-specific write logs for only one (the current) consistency interval, replication target 140 may also maintain node-specific write logs for other, previously ended, consistency intervals.

While FIG. 2 shows three, independent node-specific write logs, in some embodiments, replication target 140 may store the writes from nodes in different ways. For example, in one embodiment, replication target 140 may store writes from all nodes in a single log configured to separately maintain the node-specific writes. For example, entries for a single, multi-node write log may include a node identifier or may include some other way to determine which writes were sent from which nodes, according to some embodiments. In some embodiments, node-specific write logs 220, 230, and 240 may be stored on disk, while in other embodiments they may be kept only in memory. Although, when maintaining such write logs in memory, replication target 140 and/or nodes 110, 112, and 114 may be configured to maintain recovery information, such as an in-progress writes scoreboard style bitmap, or synchronous write logs for use in case of a system error or crash. In other embodiments however, writes from nodes 110, 112, and 114 may be maintained both on disk and in memory. In general, replication target 140 may be configured to store writes from nodes in any fashion suitable of storing the write data while allowing access the data on a node-specific basis.

After a current consistency interval ends, such as interval 3 in FIG. 2, replication target 140 may generate a consistency checkpoint or snapshot, or otherwise save the data from writes during the interval to a replication store, such as checkpoint store 250. FIG. 2 illustrates checkpoint store 250 including two consistency points already saved, interval 1 consistency point 260 and interval 2 consistency point 270. In one embodiment, a consistency snapshot of the entire data (not just the data written in the current consistency interval) may be generated. In other embodiments however, only those changes to data made during the current interval may be stored in checkpoint store 250 or other replicated data store.

While FIG. 2 illustrates three nodes, three node-specific write logs and three intervals, other embodiments may include many more such nodes, logs and intervals. Logs may also be combined, so that one log includes entries from several nodes or for several purposes. Furthermore, saving consistency points in a checkpoint store on replication target 140 is only one of many possible methods for storing replicated data. In other embodiments, consistency point data may be stored on devices separate from replication target 140, or even forwarded to completely separate replication system.

FIG. 3 is a block diagram illustrating, according to one embodiment, the logical flow of communication between a node, an interval coordinator, and a replication target while implementing consistency interval marker based replication. The logical communication flow illustrated in FIG. 3 represents an example exchange among interval coordinator 120, node 110, and replication target 140 during a consistency interval transition (i.e. the ending of one interval and the start of another). Thus, as described above, node 110 may send writes, each including the ID of the current interval, to replication target 140 and replication target 140 may, in some embodiments, send acknowledgments back to node 110, as illustrated by arrows 320 and 325.

Additionally, in some embodiments, node 110 may maintain or update a recovery map or log indicating blocks or regions of blocks that have been changed. For example, a dirty region bitmap, in which each bit represents a range of data blocks, may be maintained, either for each node, or for all nodes together, according to different embodiments. Alternatively, in other embodiments, a sequential, synchronous, log of all writes may be maintained during the current interval and flushed once a consistency checkpoint or snapshot has been generated for the internal by replication target 140. In general, the term “recovery map” is used herein to refer to any sort of data structure used to store or maintain recovery information regarding the writes sent by the source nodes to the replication target, including, but not limited to, dirty region tracking, synchronous data logs, metadata logs, data change objects, etc. Likewise, the term “log” is used herein to refer to any sort of data structure used to store or maintain a record of operations, such the data being written, in a manner that allows retrieval of individual operations as discrete items which can be ordered in a sequence using a unique identification key associated with each item, including, but not limited to, logs, databases, etc.

Thus, in some embodiments, node 110 may also update a recovery map after sending a write to replication target 140. For instance, node 110 may set (to 1) bits in dirty region bitmap corresponding to the blocks being written. After receiving acknowledgement from replication target 140, node 110 may then clear those bits (to 0).

In one embodiment, a single, combined, recovery map may be maintained for all data written by all nodes. In other embodiments, however, a separate recovery map may be maintained for each node. Maintaining a separate recovery map for each node may allow an interval coordinator, such as interval coordinator 120, to perform recovery processes for a crashed node based on the contents of that node's recovery map. Please note that while in some embodiments, each node may interact with and update its own recovery map, in other embodiments, a single recovery process may maintain all the nodes' individual maps based upon information supplied by the nodes.

In certain embodiments, each node may maintain two such recovery maps, one for the currently active consistency interval, and one for the immediately previous consistency interval. Since, in some embodiments, nodes may be sending writes for a new consistency interval while the previous (just ended) interval is still being processed, such as for block conflict resolution. For example, in one embodiment, block conflicts may still be being resolved while nodes are already sending writes (to non-conflict blocks) for the next interval. Thus, when using two recovery maps, a node may use one as an active map for recording changes made during the current interval and may use the other as a replay map for the previous interval. A node may swap the two maps (i.e. make the active map the replay map and clear out the replay map to make it the active map) at interval transitions. Some embodiments may keep maps for more than one previous interval, allowing more flexibility in conflict resolution at the expense of greater memory consumption. As the workings and use of recovery maps, and recovery information in general, are well understood in the art, they will not be discussed in detail herein.

At some point interval coordinator 120 may determine that it is time to end a current interval and thus may send a consistency interval end message to node 110, as represented by arrow 300 in FIG. 1. As discussed above, there are multiple ways that interval 120 may determine when to end a consistency interval. In response to the consistency interval end message, node 110 may send an acknowledgement message back to interval coordinator 120, as indicated by arrow 305. Also, as noted above, node 110 may also suspend completion of writes in response to receiving the interval end message, according to some embodiments. When suspending completion of writes during an interval transition, node 110 may, in some embodiments, continue to send writes to replication target 140, but may not acknowledge the completion of those writes to any application that performed the write originally. Thus, if the node crashes during the interval transition, the application cannot assume that the writes were completed and thus may have no expectations regarding the state of the relevant data, according to some embodiments.

After receiving acknowledgment messages from all nodes in the system, interval coordinator 120 may send another message to all the nodes. In some embodiments, interval coordinator 120 may send a message including the ID of the new interval that is starting, as indicated by arrow 310A. In other embodiments, however, interval coordinator 120 may include the new interval ID in the interval end message and, after receiving acknowledgements from all nodes, interval coordinator 120 may send a message signaling the nodes to resume suspended write completions. When resuming suspended write completions, node 110 may notify the application that originally performed a write that was suspended of the successful completion of that write, according to certain embodiments.

After node 110 has sent all writes for the current interval (that is, the interval just ending), node 110 may, in some embodiments, send a consistency point or a consistency interval marker message to replication target 140. Node 110 may inform replication target 110 that it has finished sending writes for an ending interval in a number of ways.

In some embodiments, node 110 may send a specific consistency interval marker message. In other embodiments, however, node 110 may include a consistency point indicator in the first write of the new interval. After receiving consistency interval markers from all nodes in the system, replication target 140 may send a message, such as a interval transition message, to interval coordinator 120 indicating that all writes for the ending interval have been sent by the nodes, as indicated by arrow 315.

In some embodiments, interval coordinator 120 may wait until receiving an interval transition message from replication target 140 indicating that all nodes have sent their respective consistency interval markers before sending a consistency interval ID message to the nodes, as indicated by arrow 310B. Thus, in some embodiments, interval coordinator 120 may send the new interval ID to node 110 at the end of the current interval, such as in a consistency interval end message, while, in other embodiments, interval coordinator 120 may wait until after receiving acknowledgements of the interval transition before sending the new interval ID. In yet other embodiments, interval coordinator 120 may wait until all nodes have sent all writes for the ending interval, indicated by replication target 140 receiving consistency interval markers from all nodes, before sending the new interval ID.

Additionally, in some embodiments, the interval ID message may also indicate that nodes may resume writes and/or write completions, while, in other embodiments, interval coordinator 120 may send a separate message instructing nodes to resume writes and/or write completions. After the interval transition and after node 110 has received the new interval ID from interval coordinator 120, node 110 may then send writes including the new interval ID to replication target 140, as indicated by arrow 340. The process may continue with node 110 sending writes to replication target 140 and replication target 140 acknowledging those writes until interval coordinator 120 ends the new interval with another interval end message.

Please note that the communication flow logically illustrated in FIG. 3 regards consistency interval replication for a system in which multiple nodes are read-sharing one or more data volumes, but in which the data is not write-shared. Thus, no two nodes may be able write to the same block of data at the same time. In other words, the communication flow logically illustrated in FIG. 3 does not include any provision for block conflict resolution, as that will be described in more detail below regarding FIGS. 5-9.

FIG. 4 is a flowchart illustrating one embodiment of a method for consistency interval maker based replication, as described herein. As described above, multiple nodes, such as applications, file systems, or volume managers, etc., may send writes to a replication target including the current interval ID with each write, as illustrated by block 400. For instance, in one embodiment, nodes 110, 112 and 114 may each send writes to replication target 140 and may include the current interval ID with each write. As noted above, replication target 140 may store each write in a node-specific log or may, alternatively store all writes from all nodes in a single log or data structure allowing node-specific access, according to various embodiments.

An interval coordinator, such as interval coordinator 120, may signal the end of the current interval, as illustrated by block 410. For example, interval coordinator 120 may determine the end of the current interval according to a length of time for the interval, while other methods for determining the length of an interval may be used in different embodiments. For example, a node may request an interval transition in order to support an in-band command or to support a temporal timestamp or version. Interval coordinator 120 may send a message to each node informing the node that the current interval is ending. In response, each node may complete all in-progress writes for the ending interval and suspend completions for any new writes, as illustrated by block 420. For example, each node may proceed to send writes for the new consistency interval to replication target 140, but may not send a completion or acknowledgement to an application or process originally performing the write, as noted above. When sending new writes to replication target 140 after suspending write completions, each node may include the new interval ID with each write in order to allow replication target 140 to differentiate between writes for the previous (now ending) interval and the new interval. Additionally, each node may send an acknowledgement message to interval coordinator 120, as indicated by block 430, letting the coordinator know that the node received the end of interval message and has suspended write completions.

After receiving an acknowledgement from every node, interval coordinator 120 may, in some embodiments, send another message to each node signaling that write completions may be resumed, as indicated by block 440. In response, the nodes may complete any previously uncompleted writes by sending acknowledgments or completion messages to applications or processes originally performing the writes, as indicated by block 450. After all data for the previous (ending) interval has been delivered to replication target 140, each node may send a consistency interval marker or consistency point message to replication target 140, as indicated by block 460, and described above. Once replication target 140 has received consistency points from every node, replication target 140 may inform the interval coordinator that interval processing is completed.

Additionally, replication target 140 may generate a consistency checkpoint or snapshot for the ended interval, or alternatively, may delay generating a checkpoint or snapshot for a time sufficient to ensure that any writes delayed, due to network congestion for example, may arrive, according to some embodiments. As discussed above, replication target 140 may delay generating a consistency checkpoint or snapshot for an additional number of consistency intervals, in one embodiment. However, source nodes may continue sending writes to the replication target and may include the new interval ID with each write, as illustrated by block 470.

While the discussions above in reference to FIGS. 2-4 described consistency interval marker based replication in reference to non-write-shared storage environments, and thus, did not discuss block conflict resolution, the following discussions regarding FIGS. 5-9 will discuss consistency interval marker based replication in write-shared environment and thus will describe block conflict resolution in detail.

FIG. 5 is a block diagram illustrating, according to one embodiment, a first phase of block conflict resolution, as described herein. For instance, node one 110 and node two 112 may each have sent writes for two blocks to replication target 140 during the current interval. Node 110 may have sent writes for blocks 1 and 2, while node 112 may have sent writes for blocks 2 and 3. Replication target 140 may store the received writes in node-specific write logs, such as node one write log 550 and node two write log 560. Thus, as illustrated by FIG. 5, node one write log may include blocks 1 and 2 from node one 110 and node two write log 560 may include blocks 2 and 3 from node two 112. As noted above, the exact manner and data structure in which replication target 140 maintains the writes received from nodes 110 and 112 may vary from embodiment to embodiment.

Additionally, in some embodiments, nodes one (110) and two (112) may periodically send interval coordinator 120 lists of modified blocks that indicate the blocks modified by each respective node. Thus, node 110 may send a list of modified blocks including blocks 1 and 2 as indicated by dirty block list 500 and node 112 may send a list of modified blocks including blocks 2 and 3, as indicated by dirty block list 510. In response to receiving the lists of modified blocks from nodes 110 and 112, interval coordinator 120 may maintain node-specific lists of modified (or dirty) blocks. Thus, the dirty block list 530 from node one may include blocks 1 and 2, while the dirty block list 540 from node two may include blocks 2 and 3.

Additionally, interval coordinator 120 may maintain a preliminary block conflict list 520 and may update preliminary block conflict list 520 whenever it receives a list of modified blocks from a node. For example, interval coordinator may compare the node one dirty block list 530 and node two dirty block list 540 and determine that block 2 was written to be both node one and node two. Thus, interval coordinator 120 may generate or update preliminary block conflict list 520 to include block 2, according to the embodiment illustrated by FIG. 5. As described above, interval coordinator 120 may send preliminary block conflict list 520 to each node after sending an interval end message and may determine a final block conflict list after receiving final modified block lists from every node, as will be described below regarding FIG. 6.

FIG. 6 is a block diagram illustrating a second phase of block conflict resolution as described herein and according to one embodiment. After determining preliminary block conflict list 520, as described above regarding FIG. 5, interval coordinator 120 may send preliminary block conflict list 520 to every node, such as nodes 110 and 112. In response to receiving a preliminary block conflict list from interval coordinator 120, nodes 110 and 112 may suspend writes or completions of writes, including in-progress writes. Thus, node 110 may suspend an in-progress write to block 3, as indicated by in-progress block list 600. Additionally, node 112 may suspend an in-progress write to block 8, even though block 8 may not be a conflict block.

Since receiving an interval end message from interval coordinator 120, nodes 110 and 112 may have completed additional writes for the ending interval. For example, node 110 may have completed in-progress writes to blocks 4 and 5, and node 112 may have completed writes to blocks 6 and 7. Additionally, node 110 may have started a write for block 3, as indicated by in-progress block list 600, and node 112 may have started a write for block 8, as indicated by in-progress block list 610, as noted above. Please note that in-progress block lists 600 and 610 are illustrated in FIG. 6 for discussion and explanation purposes only. Nodes taking part in consistency interval maker based replication with block conflict resolution, as described herein, may not actually maintain such a list of in-progress writes, or may maintain such a list in a different form or format.

Nodes 110 and 112 may also send a final list of modified blocks to interval coordinator 120, according to some embodiments. For instance, node 110 may send a final modified block list including blocks 4 and 5 and node 112 may send a final modified block list including blocks 6 and 7. Thus, interval coordinator 120 may update its node-specific modified block lists, as indicated by node one dirty block list 530 and node two dirty block list 540. In response to receiving final modified block lists from nodes, interval coordinator 120 may generate and distribute to the nodes a final block conflict list, such as final block conflict list 620.

Additionally, as described above, interval coordinator 120 may include conflict-resolving instructions to each node when sending final block conflict list 620. Alternatively, interval coordinator 120 may send such conflict-resolving instructions in separate, individual message to each node, according to certain embodiments.

Regardless of whether interval coordinator 120 sends conflict-resolving instructions along with final block conflict list 620 or separately, the nodes may, in one embodiment, send additional writes to replication target 140 to resolve the block conflicts, according to the conflict-resolving instruction from interval coordinator 120. For example, interval coordinator 120 may request that node 110 complete the in-progress write of block 3, thereby resolving the conflict of block 3. Please note that since the in-progress write of block 3 from node 110 occurs after the completion of the write to block 3 from node 112, interval coordinator 120 may determine that the data for block 3 from node 110 is the final (in terms of the current consistency interval) data for block 3. Similarly, interval coordinator 120 may request that node 112 read the data for block 2 and forward it to replication target 140. Please note that interval coordinator could also have requested that node 110 read and forward data for block 2, however, in some embodiments, interval coordinator 120 may distribute conflict-resolving instructions across multiple nodes in order to limit the amount of time and network bandwidth used by each node during conflict resolution, and to take advantage of possible data caching on the individual nodes or data access hardware.

Interval coordinator 120 may send such conflict resolving instructions to nodes in various forms, according to different embodiments. For example, in one embodiment, interval coordinator 120 may simply include a list of blocks that a node is to read and send to replication target 140.

When sending conflict resolving writes to replication target 140, in response to receiving conflict-resolving instructions from interval coordinator 120, a node may mark or flag the writes as conflict-resolving so that replication target 140 may know to overwrite any previously received data for the relevant blocks with the data from the conflict-resolving writes. For example, a particular tag or flag may be included with a conflict-resolving write in one embodiment. In other embodiments, however, replication target 140 may assume that any writes including a consistency interval's ID received after that interval has ended to be conflict-resolving writes. Alternatively, in yet other embodiments, interval coordinator 120 may send replication target 140 a message indicating which blocks will be overwritten by conflict-resolving writes and thus replication 140 may be able to determine which writes from nodes are conflict-resolving writes, such as to handle the case where an earlier (non-resolving) write is received later than a conflict resolving write for an interval (which can happen if nodes process and deliver data to the target with different delays).

FIG. 7 is a block diagram illustrating the logical communication flow between a node, an interval coordinator, and a replication target while implementing consistency interval replication with block conflict resolution, according to one embodiment. Similarly to FIG. 3, described above, FIG. 7 shows the communication between node 110, interval coordinator 120 and replication target 140 for an interval transition including block conflict resolution, as described herein and according to some embodiments. Thus, FIG. 7 (like FIGS. 5 and 6) illustrates consistency interval marker based replication in an environment that includes write-shared data storage in which multiple nodes may write to the same data block, thus replication target 140 may receive multiple writes from different nodes to the same data block. As described above, node 110 may send writes to replication target 140 including the current interval ID with each write and replication target 140 may response with acknowledgement messages, as illustrated by arrows 700 and 705.

Unlike consistency interval marker based replication without block conflict resolution, consistency interval marker based replication with block conflict resolution involves nodes, such as node 110, periodically sending interval coordinator 120 lists of the blocks modified by the writes sent from the nodes, as indicated by arrow 710. Thus, periodically throughout a consistency interval, node 110 may send a message to interval coordinator 120 including a list of those blocks being modified by the writes from node 110. Node 110 may only include in such a list blocks that have been modified since the last time node 110 sent such a list to interval coordinator 120. However, in some embodiments, nodes may not send lists of modified blocks periodically, but instead may send a complete list of modified blocks to interval coordinator 120 in response to a consistency interval end message from interval coordinator 120. Interval coordinator 120 may also maintain node-specific lists of modified blocks for use in block conflict resolution, such as dirty block lists 530 and 540, described above regarding FIGS. 5 and 6.

As described above, consistency interval 120 may send an interval end message to node 110 at the end of the current interval, as shown by arrow 715. In response to the interval end message, node 110 may send interval coordinator 120 an updated list of modified blocks, as illustrated by arrow 720. As noted above, node 110 may send a list of only those blocks modified since the last time node 110 sent such a list to interval coordinator 120 (during the current consistency interval). Interval coordinator 120 may analyze the lists of modified blocks from all nodes to identify block conflicts where two nodes sent writes for the same data block. Interval coordinator 120 may send a preliminary list of block conflicts to each node as indicated by arrow 725. In some embodiments, this list may be preliminary because some nodes may not have completed all writes for the ending interval. In response to receiving a preliminary list of block conflicts, node 110 may suspend all writes to any conflict block but may, in some embodiments, send writes for non-conflict blocks in the new interval, as indicated by arrow 730. While not illustrated in FIG. 7, replication target 140 may acknowledge writes for non-conflict blocks as described above regarding arrow 705.

Additionally, after receiving a preliminary list of block conflicts from interval coordinator 120, node 110 may send a final list of modified blocks to interval coordinator 120, as indicated by arrow 740. For example, node 110 may send a list of blocks modified since the last list of modified blocks was sent to interval coordinator 120. In another embodiment, node 110 may respond to a preliminary list of block conflicts with a complete list of all blocks modified during the current interval. After receiving the final lists of modified blocks from all nodes, interval coordinator may, as described above, send a final list of block conflicts to each node, as indicated by arrow 745. In some embodiments, interval coordinator 120 may send identical messages to all nodes with a list that includes all block conflicts.

In other embodiments, however, interval coordinator 120 may send individual messages to each node with the final list of block conflicts that also includes specific instructions for that node to perform for conflict resolution. For example, as described above, interval coordinator 120 may request node 110 to read the data for a specific block and forward that data to replication target 140. When sending such conflict resolving writes to replication target 130 as indicated by arrow 750, node 110 may, in some embodiments, include an indication that the write is a conflict-resolving write and that the data in the conflict-resolving write should overwrite any other writes to the same block (within the ending consistency interval), as described above.

Interval coordinator 120 may also request that node 110 complete an in-progress write for a conflict node and in response, node 110 may send the write to replication target 140, in some embodiments including an indication that this write is a conflict-resolving write. In response to receiving conflict-resolving writes from node 110, replication target 140 may use the data from the conflict-resolving writes when generating a consistency checkpoint or snapshot for the ending consistency interval. Additionally, replication target 140 may, in some embodiments, send an acknowledgment message to node 110 indicating that replication target 140 received the conflict-resolving writes, as described above regarding arrow 705.

After completing all conflict-resolving instructions from interval coordinator 120, whether included with the final list of conflict blocks or sent in individual messages, node 110 may, in some embodiments, send a consistency point or consistency interval marker message to replication target 140, as indicated by arrow 760. As described previously, once replication target 140 has received consistency point messages from all nodes, replication target 140 may send an interval transition message, as indicated by arrow 765, to interval coordinator 120 reporting that all nodes have finished all conflict-resolving processing and have sent their respective consistency point messages. Thus, interval coordinator 120 may determine that all processing for the ending interval may be complete, according to one embodiment.

FIG. 8 is a flowchart illustrating, according to one embodiment, a method for consistency interval marker based replication with block conflict resolution, as described herein. As illustrated by block 800, at the end of a consistency interval, interval coordinator 120 may signal the end of the interval, as described above and the nodes may suspend write completions, as indicated by block 810 and discussed above.

As illustrated by block 820, each node may send a final list of blocks modified during the consistency interval. For example, in one embodiment, each node may send a single, complete, list of all blocks modified since the start of the consistency interval. In another embodiment, each node may periodically send lists of modified blocks and may only send, as a final modified block list, a list of those blocks changed since the last modified block list was sent to interval coordinator 120.

Interval coordinator 120 may also analyze the received list of modified blocks for each node to determine whether there are any blocks in conflict, as illustrated by block 830, as discussed above. If there are blocks in conflict, interval coordinator 120 may send a message to all nodes including the final list of conflict blocks, as indicated by block 835, and, in response, the nodes may resume write completions for blocks that are not in conflict, as indicated by block 840. Additionally, interval coordinator 120 may resolve the block conflicts, as illustrated by block 850 and as described in detail below regarding FIG. 9. If there were no conflicts, as indicated by the negative output of block 830, the interval coordinator may simply send a message acknowledging that the receipt of the lists of modified blocks from each node, as indicated by block 860 and in response, the nodes may resume any suspended writes or write completions, as illustrated by block 870.

As described above, interval coordinator 120 may send messages to certain nodes requesting the forwarding of data for conflict blocks to replication target 140 and may also request the completion of suspended in-progress writes to resolve a block conflict, according to some embodiments. After resolving all block conflicts, or if there were no block conflicts, the interval coordinator may signal the start of a new interval, as indicated by block 880. For example, the interval coordinator may send a message to all nodes including the new interval's interval ID, in some embodiments. In other embodiments, however, the nodes may have already received the new interval ID, and may already be sending writes including that interval ID, and thus the interval coordinator may send a message informing all nodes that all conflicts for the ending interval are resolved, and thus the nodes may begin or resume sending writes for all blocks, including the previous conflict blocks, as described above. Additionally, in some embodiments, the nodes may, in response to receiving a message regarding the completion of interval transition processing from interval coordinator 120, perform any node-specific processing, such as cleaning up recovery information stored for the completed consistency interval, as discussed previously.

FIG. 9 is a flowchart illustrating one embodiment of a method for block conflict resolution as described herein. After receiving a final list of modified blocks from each of the nodes, as illustrated by block 900, interval coordinator 120 may analyze the list of modified blocks to determine any block conflicts, as illustrated by block 910, and described above. For example, the interval coordinator may go through the list from each node comparing it to the lists from every other node to determine blocks written to by more than one node. After determining a list of blocks with conflicts, interval coordinator 120 may send the list of block conflicts to each node, as indicated by block 920. Interval coordinator 120 may then proceed to resolve the block conflicts. For each block conflict the interval coordinator may determine whether there is a suspended in-progress write for the block in conflict, as illustrated by block 940. If there is an in-progress write for a conflict block, interval coordinator 120 may request that the node holding the in-progress write complete the in-progress write, thus allowing replication target 140 to overwrite any earlier writes for the block.

If there is not an in-progress write for a conflict block, interval coordinator 120 may request that a node read the data for the conflict block from primary storage 130 and forward that data to replication target 140, as illustrated by block 950. As noted above, interval coordinator 120 may also include with a final block conflict list message conflict-resolving instructions, such as for a node to read data for certain blocks and forward them to replication target 140. As discussed above, a node may include an indication that the data in a conflict-resolving write for a block should overwrite any earlier data for that block (within the current interval). Additionally, interval coordinator 120 may also send instructions for a node to complete an in-progress write for a conflict block. Thus, in some embodiments, replication target 120 may receive conflict-resolving writes for conflict blocks for the currently ending interval.

While there are still block conflicts to be resolved, interval coordinator 120 may move on and determine how to resolve the next block conflict, as illustrated by blocks 970 and 930. As interval coordinator 120 and the nodes finish resolving block conflicts for each node, interval coordinator 120 may, in some embodiments, send a message including the new consistency interval ID to the node, and in response the node may send a consistency point message to replication target 140. After all block conflicts have been resolved, as described above, replication target 140 may generate a consistency checkpoint or snapshot of the data for the consistency interval, as illustrated by block 980. However, as noted above, replication target 140 may only generate a consistency checkpoint or snapshot for the interval after receiving a consistency point from all the nodes, in some embodiments.

In-band Command with Consistency Interval Marker based Replication

In some embodiments, on-demand consistency intervals may be requested by an application, such as a file system, running on nodes in the distributed environment. For instance, in one embodiment, an application 150 may request that the current consistency interval be ended and a new consistency interval be started. An application may request a consistency interval transition at times in which the data is in a consistent state from the application's point of view. In some embodiments, an application, such as a file system, database or other application, may desire to issue an in-band command to a storage system, such as either primary storage 130 or replication target 140. For instance, a file system may request a replication target create a snapshot or checkpoint when the data is in a particular consistent state, after all relevant updates are written to a particular database, for example. In another embodiment, a database may issue an in-band command to initiate flushing of cached or uncommitted writes, to coordinate data synchronization, or to manage cross system coordinated transactions. Similarly, an application may utilize in-band commands to commit a particular procedure or operations after writing a large batch file or other dataset. The application may request the end of the current consistency interval and issue an in-band command requesting that some action or event (such as a snapshot or incremental backup) to be performed by a storage system node, replication target device, or other process or device, according to some embodiments. In one embodiment, an in-band command may be associated with a particular consistency interval and may be executed after all the data writes for that particular consistency interval have been committed, or replayed, to storage (either to primary or secondary storage). Thus, in-band commands in association with consistency interval marker based replication may allow actions or events to be executed when the data is known to be in a particular consistency state from an application's point of view.

Additionally, a defined interval, such as a consistency interval or other interval initiated via an in-band command may also be associated with a named event, such as an application defined event, to allow subsequent access to data of a continuous data protection store (e.g. a time-index store) at a particular point in time. For example, a database may define a named event to enable a rollback to a particular point in time. Thus, in-band command may be utilized without a replication target to define named events associated with particular points in time where data is consistent.

For example, in one embodiment, application 150 may require a specific or custom action be performed by replication target 140, such as an incremental backup or data snapshot, after a particular set of data updates are written. Thus, application 150 may issue an in-band command through node 110. After all the relevant writes are processed, node 110 may request that interval coordinator 120 end the current consistency interval, such as by sending an interval end request message to interval coordinator 120. In response to such a message, interval coordinator 120 may initiate a consistency interval transition, thus ending the current interval and beginning a next interval. The in-band command issued by application 140 may be associated with the current (ending) consistency interval to ensure that the in-band command is executed while the data is a particular consistency (or logical) state from application 140's point of view. Thus, after the end of the current consistency interval and after all relevant data writes are stored or updated on replication target 140, replication target 140 may execute an action or command indicated by the in-band command before storing any writes for the next consistency interval, according to one embodiment.

In other embodiments, the nodes themselves may store writes in spillover logs from which a replication target may read the writes for replication purposes. In yet other embodiments, writes may be written to logs by another node or device, such as replication target or another node configured to interface with a particular storage system. In-band commands may also be stored to logs with writes, according to some embodiments. According to other embodiments, an in-band command may be saved to a spillover or other persistent log after all the writes for the current consistency interval have been saved to the log. As noted above, an in-band command may be associated with a particular consistency interval, and in some embodiments an in-band command may be associated with a consistency interval by being stored in a log with the writes for that same consistency interval. In other words, a log may include markers, special records, or other mechanisms to indicate which writes, and/or which in-band commands, are a part of which intervals. In certain embodiments, an in-band command may be associated with a particular consistency interval by including an indication of the consistency interval, such as a consistency interval ID, with the in-band command.

Additionally, as described above, in-band commands may also be stored in logs with the writes for a particular consistency interval, according to some embodiments. For instance, an in-band command may be stored in a log after all the writes for a particular consistency interval are saved to the log. As with other consistency interval messages, an in-band command message may include an indication of the particular consistency interval it is associated with. Thus, replication target 140 may be configured to store an in-band command in a node specific log with the writes for the same consistency interval.

In some embodiments, in-band commands are only sent (or saved to log) at the end of a consistency interval after all the writes for that interval have been sent (or saved to log). In other embodiments, however, an in-band command may be sent (or saved to log) anytime during a consistency interval and may be held by the replication target until the end of the interval before being executing. In other words, the replication target that executes an in-band command may be configured to delay execution of the action requested by the in-band command until after all writes for the relevant consistency interval have been received (or read from log) and stored.

When using in-band commands in embodiments where writes are not being logged, a replication target may receive an in-band command and, after storing or otherwise processing the data from all the writes for the current consistency interval, may execute an action or event requested by the in-band command, according to some embodiments. For instance, after receiving an in-band command, a replication target may delay executing any action requested or specified by the in-band command until receiving notification of the end of the current consistency interval. For example, in some embodiments, a replication target may wait until it has received consistency interval markers from all relevant nodes in the distributed environment before executing a command or action indicated by an in-band command. In other embodiments, the replication target may wait until receiving an indication from a consistency interval coordinator that the current consistency interval is over before executing an in-band command. Thus, on-demand consistency interval transitions may allow actions to be performed at particular points (in terms of data consistency) in the replication of data.

While mostly described herein regarding performing application requested commands on a replication target device, such as replication target 140, in-band command may also be used to perform actions or commands on a primary storage device, such as primary storage 130. For instance, in-band commands may provide a mechanism for triggering actions or events at known logical points in the data (from the application point of view) on a primary storage system for snapshots, backup services, etc, according to various embodiments. Additionally, while mainly described herein regarding performing replication services on data, in-band command may also be used to perform other actions, such as informing a remote system that a particular file (such as a database) is in a particular consistent state, such as for triggering the remote system to read the file for further analysis or processing, according to some embodiments.

FIG. 10 is a flowchart illustrating one embodiment of a method for consistency interval marker based replication including in-band commands. Thus, as indicated by block 1000, nodes in a distributed storage environment, such as nodes 110, 112, and/or 114, described above, may send replicated writes to a replication target device, such as replication target 140, also described above. In some embodiments, the nodes may send the writes directly to replication target 140, while in other embodiments, nodes may use spillover logs to persistently store the writes (such as to protect against data loss or corruption in the event of a system crash or failure). In such embodiments, replication target 140, or a reader node configured to communicate with replication target 140, may be configured to read writes from the spillover logs and update replication storage according to those writes.

As illustrated by block 1010, a node may, in some embodiments, request a consistency interval transition. For example, an application, such as file system executing on nodes 110, 112 and/or 114, may desire to have a replication target, or other remote system, perform an action while the replicated data is in a particular (possibly application-specific) consistency state. Thus, in one embodiment a node may send a consistency interval transition request message to an interval coordinator. In response, the consistency interval coordinator may initiate a consistency interval transition by ending the current consistency interval, as indicated by block 1020 and described above. After the nodes have completed all writes for the current (ending) consistency interval, possibly including any required block conflict resolution, the node requesting the interval transition may send an in-band command message to the replication target as the last message for the current (ending) consistency interval, according to some embodiments.

As noted above, the node may also save the in-band command to a spillover log and rely upon the replication target or a reader node, to retrieve the in-band command from the spillover log. After all the writes and the in-band command have been sent (or saved to log) the nodes may resume sending writes to the replication target for the new consistency interval, as indicated by block 1040, in one embodiment. In other embodiments, as described above, the nodes may already have been sending (or saving to log) writes for the new consistency interval even while processing for the ending interval is still ongoing. For example, writes and in-band commands may include an indication of which particular consistency interval they are associated with and thus may be sent or saved to log before processing of an ending interval is completed without risking data corruption or inconsistency between the consistency intervals.

In some embodiments, as described above, nodes may be configured to temporarily suspend completion of writes during the transition between consistency intervals. Thus, in some embodiments, after the interval coordinator initiates an interval transaction, the nodes may hold all current and newly received writes for completion until after the interval transition is completed (including any required block conflict resolution, in some embodiments) and the interval coordinator as instructed the nodes to resume write completions.

While the discussion of FIG. 10 above regards how the nodes of a distributed environment may implement in-band commands using on-demand consistency intervals, FIG. 11 is a flowchart illustrating one embodiment of a method for receiving and executing in-band commands implemented using on-demand consistency intervals. As indicated by block 1100, a replication target, such as replication target 140, may receive replicated writes from nodes in a distributed storage environment, as described above. In some embodiments, the replication target may receive writes directly from the nodes, while in other embodiments, the nodes may store the writes to one or more log files and replication target 140 may be configured to read the writes from the log files. In certain embodiments, a separate device, such as reader node 1220 may either receive the writes or read the writes out of the log files on behalf of replication target 140 and deliver the writes to replication target 140. Additionally, in some embodiments, replication target 140 may receive an in-band command, either directly or via a spillover log, from one or more of the nodes, as indicated by block 1110. As with the writes, replication target 140, or in some embodiments, a separate device such as reader node 1220, may receive the in-band commands either directly, or via one or more persistent log files, according to various embodiments. As noted above, an application, such as a file system executing on the nodes of the distributed storage network, may require that replication target 140 perform some action or event, such as an incremental backup, data snapshot, or other action, and may request a consistency interval transition to ensure that the action is performed while the data is in a particular, application specific, state. Thus, as indicated by block 1120, replication target 140 may also receive a consistency interval marker from one or more of the nodes, according to various embodiments. In other embodiments, replication target 140 may receive an indication of the consistency interval transition from a consistency interval coordinator, such as interval coordinator 120.

After the end of a consistency interval and after storing data for all the writes associated with the (ending) consistency interval, as indicated by block 1130, replication target 140 may execute the in-band command, as indicated by block 1140. As described above, the in-band command may indicate one or more actions, command, or events, to be performed once all the writes for the associated consistency interval are stored. For example, an in-band command may be used to request an incremental backup, a global snapshot, or any other action, while the data is in the particular state. Thus, in-band commands may be associated with particular consistency intervals and executed after ensuring that all writes for the particular consistency interval are stored, such as to replicated or secondary storage, according to some embodiments. After executing the in-band command, the replication target may begin to receive writes for the next consistency interval from the nodes, as indicated by block 1150. In some embodiments, however, replication target may begin to receive writes for the next interval prior to completing execution the in-band command or, in some embodiments, prior to completing the storing of the writes for the previous consistency interval. In some embodiments, when replication target 140 receiving writes for a next consistency interval before completing processing of the previous interval, replication target 140 may hold the received writes while completing the processing for the previous interval. For example, in one embodiment replication target 140 may be configured to receive and store, such as in a log file, new writes for a new consistency interval while processing writes and/or in-band commands for a previous consistency interval.

FIG. 12 is a block diagram illustrating one embodiment of a distributed system for implementing in-band commands in conjunction with on-demand consistency intervals and persistent spillover logs. As described above, an application may issue in-band commands to trigger various actions or events to be performed when the data is in a particular application-specific states, such as after a particular set of updates to the data are written. In order to ensure that the action requested by the in-band command is executed by the data is in the particular state, the application may also request a consistency interval transition to occur at the point when the data is in that state. Also as described above, the nodes of the distributed system may store writes and in-band commands to persistent spillover logs, such as logs 1230A and 1230B. The use of persistent spillover logs may allow data recovery and/or prevent data loss or corruption in the event of system failure, according to some embodiments. Thus, if the system fails before the data writes in the logs can be committed to replication storage, such as replication target 140, upon system recovery, the writes may be read from the persistent logs by replication target 140 or by reader node 1220 in order to properly store those writes to storage on replication target 140. In some embodiments, node reader node 1220 and replication target 140 may be a single system, while in other embodiments the two may be separate, distinct systems. For instance, reader node 1220 may read the writes stored in log 1230A and/or 1230B and update storage on replication target 140 accordingly. Additionally, reader node 1220 may also read one or more in-band commands stored in logs 1230A and 1230B and may initiate commands, actions or events indicated by the in-band commands.

As noted above, an in-band command may be associated with a particular consistency interval and may be stored in a log along with the writes for the same consistency interval. In some embodiments, a spillover log may group writes (and in-band commands) according to the particular consistency interval with which they are associated. For instance, after storing all the writes and any in-band commands associated with a current consistency interval, a node may store a marker record in the log that indicates the transition between consistency intervals. Thus, when reading from logs 1230A and 1230B, reader node 1220 may be configured to first update replication target 140 according to the writes for the current consistency interval, but may also be configured to read in-band commands associated with the current consistency interval and execute the actions indicated by the in-band commands before reading data writes for the next consistency interval from the logs. In other embodiments, rather than store a marker record in a persistent log indicating a transition between consistency intervals, the records of the log, both for writes or in-band commands, may include an indication of a particular consistency interval. In general, any suitable method for associating replicated writes and in-band commands with particular consistency intervals may be utilized with on-demand or periodic consistency interval marker based replication.

FIG. 13 is a flowchart illustrating one embodiment of a method for in-band commands using spillover logs during consistency interval marker based replication. As described above, nodes may store replicated writes to log files, as indicated by block 1300, rather than send the write requests directly to a replication target. As noted previously, the use of persistent spillover logs may reduce or eliminate data loss or corruption in the event of system failure during replication, according to some embodiments. During replication, an application, such as a file system may require that a particular action or event be performed when the data is in a particular (possibly application-specific) state and so an application, or a node on which the application is executing, may request an on-demand consistency interval transition, as indicated by block 1310. For instance, a node may send an interval transition request message to an interval coordinator and in response the interval coordinator may initiate a consistency interval transition, as indicated by block 1320. The node may then save the in-band command message to the log file, as indicated by block 1330. In some embodiments, however, the node may save the in-band command to the log before requesting the interval transition. After the interval transition is complete, including any required block conflict resolution, the nodes may begin storing writes for the next interval into the log file, as indicated by block 1360. As described above, in some embodiments, nodes may send writes, and in-band commands, directly to a replication target device and the replication target device may store the writes and any in-band commands to log files until the end of the current consistency interval. In some embodiments, separate, individual log files may be used for each, respective consistency interval, while in other embodiments, writes and in-band commands for multiple consistency intervals may be stored using a single log file.

Creating Temporal Volumes Using Consistency Interval Techniques

In some embodiments, consistency interval techniques may be utilized for versioning and/or timestamping when creating temporal volumes. Temporal volumes may be volumes that store multiple versions of data rather than just the most recent version of data, according to some embodiments. A volume that maintains non-present data in addition to the present data may be considered a temporal volume or time-index volume. That is, a temporal volume maintains the history of data stored on it, thus providing a way for the application to retrieve a copy of the data at any time in the past. A temporal volume may be configured to record every version of data, and thus may maintain every change saved to every block of data. In many instances, a temporal volume may be configured to record versions periodically. Thus, when a temporal volume receives a new write, rather than simply overwriting the previous version of the data, the new data is saved in a different location and “chained” to the previous version so that individual versions may be read or built from the temporal volume. When saving versions periodically, a temporal volume may be configured to initially save a new copy of a block data when a new write is received for that block but may also be configured to overwrite that new copy with additional writes for that block until it is time to save a new version.

In general, a normal (non-temporal) write on a temporal volume may not achieve temporality. Instead, normal writes generally overwrite any previous version of the data. For example, when saving changes to a file, a normal write will generally just overwrite the previous version of the file in place. To keep a history of changing data, special temporal write interfaces may be used to provide timestamps for new data. When a normal write is used, the new data simply overwrites the old data, but during a temporal write, the new data may be chained to the old data and may be stamped, or otherwise associated, with a timestamp. For example, when a new temporal write is received that includes a new copy of data for a particular data block, rather than overwriting the older version of the data in the data block, as would generally be done for a normal write, a temporal write allocates a new data block for the new version of the data and chains or links the new version to the old version, such as by updating metadata for the versions of the data.

Temporal volumes may, in some embodiments, provide special interfaces for temporal IOs. During a temporal write, the new data may be chained to the old data and stamped with a timestamp provided by a user, application, or that may be obtained from a system clock based on some periodic checkpointing policy. Timestamps may be considered an important parameter of a temporal volume since it is through timestamps that temporal volumes may achieve versioning. In distributed systems where data volumes may be shared across multiple nodes it may be very difficult to provide a global timestamp to all nodes at the same time in a consistent manner. Thus, it may be difficult to move from one version of temporal data to another without compromising the consistency of point-in-time, frozen, or versioned data. CI/BCR may be used to provide “on-demand” or “periodic” consistency checkpoints for timestamping or versioning in temporal volumes in distributed (or clustered) environments. CI/BCR may provide an efficient and scalable method to help all nodes switch from one version to another in a consistent manner.

A volume manager (or temporal volume) may not interpret timestamps, but instead may simply require that timestamps be comparable with each other, according to some embodiments. By requiring that timestamps be comparable, it should be possible to arrange timestamps, and thus temporal versions, in order. This may be required for temporal read operations and for getting information about the history of the data, in some embodiments. Timestamps may be integer data types in some embodiments. In other embodiments, timestamps may also be actual system times (such as the number of seconds from an epoch), version numbers or simply incremental counters. However, by not interpreting timestamps, temporal volumes may not be able to guarantee the coherence of time as shown by the timestamps. In some embodiments, t may be up to the relevant application or even a user to maintain the coherency of timestamps. In other words, a temporal volume or temporal volume manager may not be configured to analyze timestamps to ensure that consecutive timestamps are used in a correct or appropriate order and also may not ensure that the same format of timestamps are used consistency, according to some embodiments. However, in other embodiments, a temporal volume or temporal volume manager may be configured to verify consistent and coherent use of temporal timestamps.

Additionally, CI/BCR enabled distributed systems may be configured feed data from several sources (such as nodes 110, 112 and/or 114) into logs that may then be used on a second system as a source of data to feed into a temporal volume store. Feeding to temporal volumes offline may have an advantage that the overhead of temporal writing may not be in the IO path. Instead, the temporal writing may be performed out of band and at some point after the original writing of the data to primary storage. Also, CI/BCR checkpointed time-index volume stores may provide consistent snapshots of shared volumes in distributed environments at checkpointing interval granularity, according to some embodiments.

In distributed environments where volumes may be shared among multiple nodes, it may be important that any individual temporal write that depends upon an earlier temporal write to be associated with an equal or later timestamp or temporal version than that of the earlier write. By ensuring that later writes dependent upon earlier writes are associated with (or included with) the same or later timestamp may help ensure that the data of the temporal versions is consistent. In other words, a snapshot of data at a point-in-time corresponding to a timestamp of a later writes may be inconsistent if earlier write, on which the later write depends, is associated with a greater timestamp hence is part of a later version of the data.

In general, unless version information is updated on all nodes in a consistent manner, a data image obtained through a temporal interface for a given timestamp or version may not be consistent from an application's point of view. In other words, not switching to a next timestamp or version consistently may result in inconsistent or corrupted data derived out of temporal volumes as dependent writes may be issued from different nodes in distributed systems all the time. Temporal volumes may not be able to provide consistent point-in-time image of volumes in distributed systems without being aided by some technique to find a consistent checkpoint in IO stream across nodes when they can switch to a next timestamp without comprising the consistency of versioned data. In some embodiments, “on-demand” consistency intervals may allow all nodes to switch from version to version consistently in an IO efficient and scalable manner.

FIG. 14 is a block diagram that illustrates the logic flow of communication between nodes and an interval coordinator during on-demand consistency interval transitions for providing consistent timestamps for a temporal volume, according to one embodiment. As described above, nodes sending replicated writes for a temporal volume may be configured to request on-demand consistency intervals in order to allow multiple nodes to transition between timestamps for temporal data in a uniform and coordinated manner. Thus, an application that may be executing on multiple nodes in a distributed environment, such as application 150, may issue commands or messages to one or more nodes 110 regarding the changing from one timestamp to another for temporal data. Thus, as illustrated in FIG. 14, application 150 may issue or send timestamp freeze messages 1420 to nodes 110A and 110B requesting a change from one timestamp (T2) to another. In response, each of nodes 110A and 110B may send a message 1425 to interval coordinator 120 informing interval coordinator 120 of the timestamp change and requesting a consistency interval transition to coincide with the change in timestamps. In response to receiving the messages from the nodes, interval coordinator 120 may send back timestamp acknowledgement messages 1430 to the nodes, in some embodiments. The nodes may, in some embodiments, be configured to hold all current and incoming writes for completion until receiving a timestamp acknowledgement message from interval coordinator 120.

In some embodiments, interval coordinator 120 may be configured to wait until receiving a changing timestamp message 1425 from every node in the system before sending any timestamp acknowledgement messages 1430 to any of the nodes. For example, as illustrated by FIG. 14, node 110A may receive the timestamp freeze message 1420 from application 150 first (before any other node) and may, in response, send changing timestamp message 1425 to interval coordinator 120. As described above, in response to receiving a timestamp freeze message 1420 from application 150, node 110A may be configured to hold for completion all writes received after timestamp freeze message 1420 until node 110A receives an timestamp ack message 1430 from interval coordinator 120. Thus, in some embodiments, if node 110A receives a write after timestamp freeze 1420, node 110 may process the write, but may not return an acknowledgment of write completion, such as back to application 150, until after receiving timestamp ack message 1430 from interval coordinator 120.

Having nodes hold writes for completion until after receiving timestamp ack messages 1430 from interval coordinator 120 may, in some embodiment, help ensure that all nodes transition between timestamps at the same time (logically with respect to the IO stream of data) and may also ensure data consistency across the timestamp change. For example, application 150 may send a freeze timestamp message 1420 to nodes 110A and 110B. Node 110A may receive the freeze timestamp message before node 110B and may also receive a new write W, as well. As described above, the new write W is processed by node 110A, but since it was received after the freeze timestamp message, it may be part of the next timestamp, not the timestamp that was just frozen. In the meantime, node 110B may receive a write W′ that is dependent upon write W. As noted above, a write W′ is dependent upon another write W if, from the application's point of view, the data for the write W is required for the data of write W′ to make sense. Thus, in this example, node 110B has received a write W′ that is dependent upon write W (received by node 110A) prior to node 110B receiving the freeze timestamp message 1420 from application 150. However, since node 110A received write W after receiving the freeze timestamp message 1420 from application 150. Thus, node 110B will include write W′ in the current (just frozen) timestamp while node 110A will include write W, on which write W1 depends, in the next timestamp.

However, by requiring that all nodes hold for completion all writes received after a freeze timestamp message until after receiving a timestamp ack message 1430 from interval coordinator 120, the data consistency error described above may be prevented. For instance, in the above example, after node 110A receives the timestamp freeze message 1420 from application 150, node 110A may hold for completion write W. Thus, since application 150 has not received completion acknowledgment regarding write W, application 150 may not send write W′ that depends upon write W. Thus, node 110B will not receive write W′ before receiving the freeze timestamp message 1220 from application 150. After both nodes (110A and 110B) have sent changing timestamp messages 1425 to interval coordinator 120 and received timestamp ack messages 1230 from interval coordinator 120, node 110A may then send application 150 an ack of the completion of write W. Application 150 may then issue write W′, however, since now both write W and write W′, which depends upon write W, are both included in the same version of the temporal data, the potential data consistency error may be avoided.

FIG. 15 is a flowchart illustrating one embodiment of a method for on-demand consistency intervals for temporal versioning. As described above, nodes in a distributed environment may receive and process writes from an application, such as a file system, executing on one or more of the nodes, as illustrated by block 1500. The nodes may, in some embodiments, be configured to associate each write with a temporal version ID or timestamp for replicating the writes to a temporal volume configured to maintain multiple versions (e.g. a version history) of the data. As described above, consistency interval marker based replication may be utilized to ensure that all of nodes transition between timestamps (and hence between temporal versions) in a consistent and coherent manner. Timestamps may be changes periodically, such as every 5 minutes, according to various temporal versioning and/or checkpointing policies, in some embodiments. Thus, the application sending the writes may determine when to transition between temporal volumes, and thus when to change timestamps. In order to change timestamps the application may, in some embodiments, send timestamp freeze messages to all nodes in the distributed environment, as indicated by block 1510. For example, the application, such as application 150, may send a message to each node indicating a transition between timestamps and that may include a new timestamp.

In some embodiments, each node may, in response to receiving a freeze timestamp message, perform various actions needed to transition between one timestamp and the next. For instance, in some embodiments, a node may associate all writes in a current temporal data cache with the timestamp and may issue commands or send messages to commit those cached writes to temporal storage as part of a the (just frozen) version, as described above. Additionally, a node may send a changing timestamp message to an interval coordinator in order to request a consistency interval transition to coincide with the timestamp (and temporal version) transition, as illustrated by block 1520. Additionally, the node may, in some embodiments, be configured to begin using a new timestamp and to hold for completions writes received after receiving the freeze timestamp message from the application, as indicated by block 1530. As described above, by holding newly received writes for completion, all nodes may be able to transition to the new timestamp in unison (with respect to the order of writes in the IO stream) and in consistent manner, thus helping to ensure data consistency for the temporal versions.

In response to receiving a changing timestamp message from one of the nodes, the interval coordinator may initiate a consistency interval transition, as illustrated by block 1540 and according to some embodiments. As described above, initiating a consistency interval transition may involve ending the current consistency interval, resolving any block conflicts between the nodes, informing the nodes about the transition, and potentially informing replication targets about the transition. After completing the consistency interval transition, the interval coordinator may send timestamp ack messages to each node, as indicated by block 1550. In some embodiments, the interval coordinator may be configured to wait until it has received a changing timestamp message from each and every node before sending a timestamp ack to any one node. Waiting to receive changing timestamp messages from every node before sending any timestamp ack messages may, in some embodiments, help ensure data consistency for both the ending temporal version and the next temporal version. For instance, using consistency interval transitions that coincide with temporal timestamp transitions may prevent a later write that is dependent upon an earlier write from being associated with a later temporal timestamp (and hence with a later temporal version) that the earlier write.

According to some embodiments, a node may, in response to receiving the timestamp ack message from the interval coordinator, resume the completion of writes and may use the new timestamp when processing received writes. For instance, in some embodiments, a node may maintain a cache of data for all writes received since the last temporal version was created. When a new write is received data for that write is either added to the cache or a previous version of that data (received after the last temporal version) is overwritten. Thus, when the next temporal version is initiated by the application, the node's cache may include a single version of all the data that changed since the previous temporal version.

While the descriptions regarding FIGS. 14 and 15 above refer to on-demand consistency intervals, in some embodiments, periodic rather than on-demand consistency intervals may be utilized in conjunction with temporal volumes. FIG. 16 illustrates the logical flow of communication between nodes and an interval coordinator regarding timestamps for replicating data to a temporal volume, according to one embodiment. As illustrated in FIG. 16, interval coordinator 120 may send consistency interval start messages 1640 to nodes, such as nodes 110A and 110B, operating in a distributed environment. As with the examples above, nodes 110A and 110B may be sending writes for a temporal volume, such as replication target 140. In some embodiments, interval coordinator 120 may be configured to implement periodic consistency intervals and nodes 110A and 110B may be configured to transition between timestamps, and hence temporal versions, in tandem with the changing consistency intervals. Thus, when nodes 110A and 110B receive consistency interval start messages 1640 from interval coordinator 120, they may be configured to freeze all current writes using the current timestamp and begin the next timestamp for the next version of the temporal data.

Additionally, in some embodiments, nodes 110A and 110B may be configured to send consistency interval start ack messages 1645 back to interval coordinator 120 in response to receiving consistency interval start messages 1640. Also, nodes 110A and 110B may be configured, according to some embodiments, to hold for completion all writes received after the consistency interval start message 1640. In one embodiment, nodes hold writes for completion until receiving a resume writes messages 1650 from interval coordinator 120. As with on-demand consistency intervals, interval coordinator 120 may be configured to wait until receiving consistency interval start ack messages 1645 from all nodes before sending a resume writes message 1650 to any node. Thus, all nodes may transition between temporal versions (using timestamps) in a consistent manner. After receiving a resume writes message 1650 from interval coordinator 120, nodes 110A and 110B may complete all held writes and continue processing new incoming writes using the new timestamp.

As described above regarding on-demand consistency intervals, nodes may transition between using one timestamp and the next when they receive a consistency interval start message 1640 from interval coordinator 120. Thus, any writes received after a consistency interval start message 1640 may be included in the next version and not included in the current (just frozen) version. As noted above, any of various methods for determining or setting the next timestamp may be utilized with periodic consistency intervals when replicating writes to temporal volumes.

FIG. 17 is a flowchart illustrating one embodiment of a method for periodic temporal versioning based on periodic consistency interval marker based replication. As described above and illustrated by block 1700, nodes in a distributed environment may be configured to received replicated writes from an application 150, such as a file system, and process those writes, such as for replication to a temporal volume. For example, nodes 110A and 110B may receive and process writes for replication target 140, which may represent a temporal volume according to some embodiments. Instead of the application determining when to transition between one temporal version and another, as described above regarding FIGS. 14 and 15, in some embodiments consistency intervals may be used for temporal versioning. Please note however, that the temporal version may not actually be frozen or generated at the time that a consistency interval transition occurs, but instead the consistency interval transition may determine where in the series of writes (e.g. in the IO stream) where he temporal version should occur. Thus, in the same way that a consistency interval transition may determine which writes are associated with particular consistency intervals, in some embodiments consistency interval transitions may also determine which writes are associated with particular temporal versions.

As illustrated by block 1710, an interval coordinator 120 may initiate a consistency interval transition. As described previously, a consistency interval may determine when to end a current consistency interval based upon any of a number of factors. For example, in some embodiments, consistency interval 120 may be configured to generate consistency intervals based on a periodic length of time, every 5 minutes for example. In other embodiments, other factors, such as the number of writes or the total amount of data being written may be used by consistency interval 120 to determine when to initiate a consistency interval transition. As part of consistency interval transition processing, consistency interval coordinator 120 may, in certain embodiments, be configured to send interval start messages to the nodes in the distributed environment. As noted above, in response to receiving an interval start message from the interval coordinator, a node may be configured to transition between one temporal timestamp and another. Nodes may determine the next timestamp to use based on any of a number of methods. In one embodiment, the nodes may all use a consistent algorithm to determine the next timestamp (or temporal version ID) to use. For example, the nodes may implement a scheme in which integer timestamp are used and each timestamp is incremented by one in order to determine the next timestamp. In another embodiment, however, the interval coordinator may be configured to determine timestamps and may include the new timestamp, or an indication of the new timestamp, in the interval start messages sent to the nodes. In yet another embodiment, the nodes may be configured to request the next timestamp from another process, such as application 150.

In general, however, the nodes may be configured to begin associating writes received after the interval start message with a new timestamp and may also be configured to hold for completion any writes received after the interval start message, as illustrated by block 1730. As described above, by holding writes for completion until all nodes may transitioned between timestamps (or temporal versions) the system may prevent data correction between the resulting temporal versions. After receiving the interval start message, each node may be configured to send an interval start ack messages to the interval coordinator to inform the interval coordinator that the node has transitioned to the next timestamp (and consistency interval) and is ready to proceed with normal write processing, as illustrated by block 1740. While note described in detail with reference to FIG. 17, the nodes and interval coordinator may also perform additional consistency interval processing, such as resolving any block conflicts, etc. in addition to performing the temporal version and/or timestamp transition processing.

After receiving interval start ack messages from each and every node in the distributed environment, the interval coordinator may be configured to send a resume writes message to the nodes, as illustrated by block 1750. In some embodiments, the interval coordinator may be configured to wait until receiving ack messages from every node before sending a resume writes message to any node in order to help prevent data corruption or inconsistencies between the two temporal versions. In the event that the consistency coordinator does not receive an ack message from a node, the coordinator may be configured to perform various times of error processing. For example, in one embodiment, the interval coordinator may be configured to send additional interval start messages, either only to those nodes that did not respond to the previous interval start message, or to all nodes. Alternatively, in another embodiment, the interval coordinator may be configured to determine that a node is not longer functioning if it fails to receive an interval start ack from the node within a certain amount of time or after resending the interval start message a certain number of times.

After a node has received a resume writes message from the interval coordinator, the node may be configured to resume completion of any held writes, such as by returning to application 150 an indication that the write was completed, according to some embodiments and illustrated by block 1760. Additionally, a node may be configured to finish timestamp transition, or temporal versioning, such as by storing records to a persistent spillover log, or by sending a timestamp change indication or a temporal version command to replication target 140, which in some embodiments may represent a temporal volume. Thus in response to receiving a resume writes message from the interval coordinator, the nodes may be configured to complete whatever processing is necessary to transition between one timestamp or temporal version to another. In some embodiments, a node may commit the current contents of a temporal data cache and start a new cache, or clear a previous cache area for current use, for saving data for newly received writes. In some embodiments, a node may be configured to utilized functions from a temporal API to send data for the current (just frozen) temporal version to a temporal volume or, in other embodiments, to another node or device that is configured to interact with the temporal volume. Thus, in some embodiment, nodes may utilize a temporal API to interact with a temporal storage system or device directly, while in other embodiments, the node may communicate, without using a temporal API, with a device or system that may be configured to utilize a temporal API to store the data for a temporal volume to a temporal storage device, such as replication target 140, according to one embodiment.

FIG. 18 is a block diagram illustrating offline feeding over temporal volumes using persistent spillover logs and consistency interval marker based replication, according to one embodiment. As described above, consistency interval marker replication may be utilized with temporal volumes to help ensure consistent versions of the temporal data. Additionally, in some embodiments, consistency interval marker replication may be utilized to implement offline replication of data to a temporal volume, as illustrated by FIG. 18. Rather than directly sending replicated writes to a temporal volume 1840, nodes of a distributed system, such as nodes 110A and 110B, may instead store information regarding both the replicated writes and about the consistency intervals to persistency spillover logs 1830A and 1830B, according to some embodiments. In one embodiment, each node of the distributed system may store information to a separate spillover log, as is illustrated by FIG. 18. In other embodiments however, multiple nodes may share a single spillover log.

As noted above, nodes 110A and 110B may store information about replicated writes to spillover logs. Additionally, the nodes may also store information regarding the consistency intervals in the spillover logs. Thus, in some embodiments, the records of the spillover logs 1830A and 1830B may be configured to allow replication of the data by reading and “replaying” the writes stored in the log. For example, by reading and processing the writes stored in the log in the order that they were stored may allow for a copy of the state of the data to be replicated on additional data volumes, such as temporal volume 1840. Additionally, since the spillover logs may also include information regarding the consistency intervals, the information in the logs may also be used to create a consistent set of snapshots of cuts of the data according to the consistency interval information.

Thus, in some embodiments, a reader node 1820 may read the data from the logs and saves the data from the writes to temporal volume 1840. Whenever reader node 1820 encounters a consistency interval boundary in a spillover log, reader node 1820 may issue commands, such as via a special temporal API, to freeze the latest copy of the data in the temporal volume with a current timestamp or ID, according to some embodiments. In one embodiment, the timestamp or ID is stored with the writes in the spillover logs. In other embodiments however, reader node 1820 may be configured to determine the current timestamp or ID in another manner. Thus, reader node 1820 stored the data from the spillover logs 1830A and 1830B to temporal volume 1840 in an incremental manner, saving versions that correspond to consistency intervals according to the information stored in the spillover logs. In some embodiments, all of the writes associated with a particular consistency interval may also be a part of a corresponding temporal version.

One advantage of storing writes to spillover logs first and then using the information from the spillover logs to create temporal versions on a temporal volume is that the overhead and bandwidth needed to store the data to the temporal volume is not part of the normal data I/O path between an application and storage. Thus, the overhead required to store the data to the temporal volume may not interfere with the normal processing of writes to primary storage. Thus, in some embodiments, the operations to store data to the temporal volumes may be considered transported to applications executing in the distributed environment. Furthermore, by allowing the nodes to store information regarding replicated writes to spillover logs, neither the application nor the nodes may have to use any special temporal operations. Instead, the reader node that reads the data from the spillover logs and stores it to the temporal volume may be the only component that uses any special temporal APIs.

FIG. 19 is a flowchart illustrating one embodiment of a method for replicating data to temporal volumes using spillover logs and consistency interval marker based replication. As described above, the nodes in a distributed environment may receive writes from an application executing with the distributed environment, as indicated by block 1900, and may utilize consistency interval marker based replication to create consistency cuts or snapshots of the data. In some embodiments, the nodes may be replicating the data to a temporal volume configured to store multiple versions of the data. Rather than send the writes directly to the temporal volume, the nodes may, in some embodiments, store the writes (and other information) to one or more persistent spillover logs, as illustrated by block 1920. As noted above, the nodes may also store consistency interval transition information to the spillover logs, as indicated by block 1930. Thus, the nodes may store all the information needed to read and replay the writes from the logs to replicate the data on additional replication targets, such temporal volume 1840, described above. When storing replicated writes to spillover logs, the nodes may associate each stored write with a current consistency interval, such as by including an identifier for the consistency interval with each writes, in one embodiment. In another embodiment, the nodes, or alternatively, the consistency interval, may store specific records in the log that represents consistency interval transitions. Thus, all writes stored in the logs between two consistency interval records may be considered part of a single consistency interval.

In order to store the data for the writes to temporal volume 1840, another components, such as reader node 1820 may read and “replay” the records from the logs and update temporal volume 1840 accordingly. For instance, reader node 1820 may read the various records from the logs in order, such as by treating the logs as FIFO queues. As each record of the log is read and processes, the data associated with the write for the record is stored to the current version of data for temporal volume 1840, as illustrate by block 1930. For instance, as described above, data for a temporal volume may first be stored in a cache location until the next timestamp change occurs, at which time the data from the cache is frozen, associated with the corresponding timestamp or version ID, and committed to storage as a temporal version. After committing the current version to storage, the cache information is cleared and the data for the next version may be stored in the cache. In some embodiments, the reader node creates a new version of the temporal data every time a consistency interval is encountered in the spillover logs. Thus, in some embodiments, the reader node may create temporal versions that correspond to the consistency interval transition information stored in the spillover logs, as illustrated by block 1960.

The description of FIG. 19 above refers mainly to storing consistency interval transition information to spillover logs and using that consistency interval information, when subsequently read to update temporal volumes, to freeze and create temporal versions of the data on a temporal volume. However, in some embodiments, temporal version IDs or timestamps may also be stored in the spillover logs and each write stored to a spillover log may be associated with a particular temporal volume or timestamp. Thus, in some embodiments, a spillover log may include information about both consistency intervals and temporal versions or timestamps and a reader node may be configured to freeze temporal versions whenever either a consistency interval transition or a temporal version freeze is indicated in the spillover logs.

FIG. 20 illustrates a computing system capable of implementing consistency interval marker based replication and block conflict resolution as described herein and according to various embodiments. Computer system 2000 may be any of various types of devices, including, but not limited to, a personal computer system, desktop computer, laptop or notebook computer, mainframe computer system, handheld computer, workstation, network computer, a consumer device such as a mobile phone, pager, or any type of networkable peripheral device such as storage devices, switches, modems, routers, etc, or in general any type of networkable computing device. Computer system 2000 may include at least one processor 2040. Processor 2040 may couple across interconnect 2050 to memory 2010 and I/O interfaces 2030. I/O interfaces 2030 may be any of various types of interfaces configured to couple with and communicate with other devices, according to various embodiments. In one embodiment I/O interfaces 2030 may represent a network interface configured to couple with and communicate over network 100 illustrated in FIG. 1, described above.

Memory 2010 is representative of various types of possible memory media, also referred to as “computer accessible media.” Hard disk storage, floppy disk storage, removable disk storage, flash memory and random access memory (RAM) are examples of memory media. The terms “memory” and “memory medium” may include an installation medium, e.g., a CD-ROM or floppy disk, a computer system memory such as DRAM, SRAM, EDO RAM, SDRAM, DDR SDRAM, Rambus RAM, etc., or a non-volatile memory such as a magnetic media, e.g., a hard drive or optical storage. The memory medium may include other types of memory as well, or combinations thereof.

In some embodiments, memory 2010 may include program instructions 2015 configured to implement consistency interval marker based replication in a clustered and/or distributed environment, as described above. In certain embodiments, program instructions 2015 may be configured to implement an interval coordinator, such as interval coordinator 120, or a shared-write coordinator, such as shared-write coordinator 150, both described above. In other embodiments, program instructions 2015 may be configured to implement a replication target, such as replication target 140, also described above. In yet other embodiments, program instructions 2015 may be configured to implement a source node, such as nodes 110, 112, and 114, also described above.

Although the embodiments above have been described in detail, numerous variations and modifications will become apparent once the above disclosure is fully appreciated. It is intended that the following claims be interpreted to embrace all such variations and modifications. 

What is claimed is:
 1. A method, comprising: sending replicated write requests from a plurality of nodes in a distributed computing environment to a shared replication target device, wherein each of the plurality of nodes is a computing entity configured to send replicated write requests in a request stream or log stream to the shared replication target device, and wherein each replicated write request is associated with a first consistency interval; requesting, by one of the nodes, a consistency interval transition from the first consistency interval to a second consistency interval, wherein the one of the nodes requesting the consistency interval transition is one of the plurality of nodes sending replicated write requests, and wherein the consistency interval transition applies to each one of the plurality of nodes; in response to said requesting, initiating the consistency interval transition to define a point in time for which data on the shared replication target device is in a consistent state, wherein the data on the shared replication target device is consistent with respect to replicated write requests from each one of the plurality of nodes to the shared replication target device for the first consistency interval; and sending a command message to the shared replication target device, wherein the command message is associated with the consistency interval transition and specifies a requested action to be performed with respect to said consistent state, wherein said sending the command message comprises inserting the command message for the consistency interval transition in the request stream or the log stream.
 2. The method as recited in claim 1, further comprising: the shared replication target device storing data corresponding to the replicated write requests to secondary storage; and subsequent to said storing data corresponding to the replicated write requests to secondary storage, the shared replication target device executing the requested action specified in the command message.
 3. The method as recited in claim 1, wherein an application executing in the distributed computing environment performs said requesting.
 4. The method as recited in claim 1, wherein said sending replicated write requests comprises: storing the replicated write requests in a log file; storing the command message in the log file after said storing the replicated write requests in the log file; and the shared replication target device reading the replicated write requests and the command message from the log file.
 5. The method as recited in claim 1, wherein said sending a command message to the shared replication target device comprises: storing the command message in a log file; and the shared replication target device reading the replicated write requests from the log file.
 6. The method as recited in claim 1, wherein the requested action comprises one or more of: creating a checkpoint, creating an incremental backup, and/or creating a snapshot of data on the shared replication target device.
 7. The method as recited in claim 1, wherein the requested action comprises reading data corresponding to the replicated write requests from secondary storage.
 8. The method as recited in claim 1, wherein the replicated write requests originate from an application executing in the distributed computing environment, the method further comprising saving data corresponding to the replicated write requests on a primary data storage device prior to said sending the replicated write requests to the shared replication target device.
 9. The method as recited in claim 1, further comprising: in response to the initiation of the consistency interval transition, each of the plurality of nodes: temporarily suspending sending replicated write requests to the shared replication target device; and subsequent to said temporarily suspending: sending a consistency interval marker to the shared replication target device; and resuming sending replicated write requests to the shared replication target device, wherein an indication of a second consistency interval is associated with each replicated write request sent after said resuming.
 10. A system, comprising: a plurality of nodes in a distributed computing environment; a shared replication target device coupled to the plurality of nodes; and a consistency interval coordinator coupled to the plurality of nodes and the shared replication target device; wherein each of the plurality of nodes is an entity configured to send replicated write requests in a request stream or log stream in a distributed computing environment to a shared replication target device, wherein each replicated write request is associated with a first consistency interval; wherein the consistency interval coordinator, in response to a request, from one of the plurality of nodes that is configured to send replicated write requests, for a consistency interval transition from the first consistency interval to a second consistency interval, wherein the consistency interval transition applies to each one of the plurality of nodes, is configured to initiate the consistency interval transition to define a point in time for which data on the shared replication target device is in a consistent state, wherein the data on the shared replication target device is consistent with respect to replicated write requests from each one of the plurality of nodes to the shared replication target device for the first consistency interval; and wherein at least one of the plurality of nodes is configured to send a command message to the shared replication target device, wherein the command message is associated with the consistency interval transition and specifies a requested action to be performed with respect to said consistent state, wherein sending the command message comprises inserting the command message for the consistency interval transition in the request stream or the log stream.
 11. The system of claim 10, wherein the shared replication target device is configured to: store data corresponding to the replicated write requests to secondary storage; and subsequent to said storing data corresponding to the replicated write requests to secondary storage, execute the requested action specified in the command message.
 12. The system of claim 10, wherein the at least one node is further configured to request the consistency interval transition, and wherein the consistency interval coordinator is configured to initiate the consistency interval transition in response to said requesting.
 13. The system of claim 10, further comprising an application executing one or more of the plurality of nodes is configured to request the consistency interval transition, and wherein the consistency interval coordinator is configured to initiate the consistency interval transition in response to said requesting.
 14. The system of claim 10, wherein in order to send the replication write requests to the shared replication target device, each of the plurality of nodes is further configured to: store the replicated write requests in a log file; and store the command message in the log file after said storing the replicated write requests in the log file; wherein the shared replication target device is configured to read the replicated write requests and the command message from the log file.
 15. The system of claim 10, wherein the requested action comprises one or more of: creating a checkpoint, creating an incremental backup, and/or creating a snapshot of data on the shared replication target device.
 16. The system of claim 10, wherein the requested action comprises reading data corresponding to the replicated write requests from secondary storage.
 17. The system of claim 10, wherein an application executing on one or more of the plurality of nodes is configured to send the replicated writes, and where one or more of the plurality of nodes is configured to save data corresponding to the replicated write requests on a primary data storage device prior to said sending the replicated write requests to the shared replication target device.
 18. The system of claim 10, wherein in response to the initiation of the consistency interval transition each of the plurality of nodes is configured to: temporarily suspend sending replicated write requests to the shared replication target device; send a consistency interval marker to the shared replication target device subsequent to said temporarily suspending; and resume sending replicated write requests to the shared replication target device, wherein an indication of a second consistency interval is associated with each replicated write request sent after said resuming.
 19. A device, comprising: one or more processors; and a memory coupled to the one or more processors, wherein the memory comprises program instructions executable by the one or more processors to implement a node in a networked computing environment, wherein the node is an entity configured to: send replicated write requests in a request stream or log stream to a shared replication target device, wherein each replicated write request is associated with a first consistency interval; request a consistency interval transition from the first consistency interval to a second consistency interval, wherein the node requesting the consistency interval transition is the node sending the replicated write requests, wherein the consistency interval transition defines a point in time for which data on the shared replication target device is in a consistent state, wherein the data on the shared replication target device is consistent with respect to replicated write requests from the node to the shared replication target device for the first consistency interval and with respect to other replicated write requests from other nodes to the shared replication target device for the first consistency interval; and send a command message to the shared replication target device, wherein the command message is associated with the consistency interval transition and specifies a request action to be performed with respect to said consistent state, wherein sending the command message comprises inserting the command message for the consistency interval transition in the request stream or the log stream.
 20. The method as recited in claim 1, wherein the command message specifies delaying execution of the request action until after all of the writes for the first consistency interval have been sent. 